Skip to content

arbiterForge/codeArbiter / plugins/ca-pi/routines/tribunal

tribunal

Verified

Run an opt-in deep codebase audit with persisted findings. Confirm cost before dispatch; filing and telemetry need separate approval.

references/lenses/infra.md

View on GitHub
# infra — lens mandate

For every security policy reference below, follow `<plugin-root>/includes/knowledge.md`
("Read security policy before a security decision"): select the repository's
context format, read the complete policy from exact `CTX-SECURITY-CONTROLS`
records in HTML mode or the full Markdown controls in Markdown mode, and read
operative scope blocks when applicable. Required policy that is missing or
unreadable blocks a security decision; scope blocks alone are not full policy.

Executed by `tribunal-lens-reviewer` under the `infra` assignment.

## Purpose / failure family
Find unsafe build, deployment and publication boundaries, or configuration
failures that compromise the promised runtime/release behavior.

## Applicability
The assigned scope includes CI, containers, infrastructure configuration,
deployment or release automation with meaningful trust or lifecycle boundaries.

## Skip conditions
No affected pipeline/deployment surface. Do not infer a hosted-service posture
for a local development fixture or a declared disposable environment.

## Scope emphasis
Workflow event to credential/artifact/publish boundary; container and deploy
configuration to actual exposed service, privilege and resource lifecycle.

## Required reading
- Finding record (`<plugin-root>/routines/tribunal/references/finding-record.md`) and review risk (`<plugin-root>/routines/tribunal/references/review-risk.md`).
- `<project-root>/.codearbiter/security-controls.md` — pipeline trust and secret
  boundaries; `<project-root>/.codearbiter/tech-stack.md` — deploy targets,
  CI/release contracts and applicable protections.

## Deterministic probes
Inspect workflow triggers/permissions, action/image references, cache/artifact
producers and consumers, publish conditions, container users/mounts and deploy
exposure. Use existing configuration/provenance receipts; do not trigger jobs.

## Review questions
- Can untrusted event data become shell syntax, credential access or executable
  candidate code in a privileged workflow?
- Can a less-trusted cache or artifact cross into release without identity checks?
- Do masked failures or mismatched protections permit publication after failed gates?
- Are image provenance, privileges, secret layers and service exposure consistent
  with the declared threat model?
- Can deploy ordering, resource exhaustion or environment drift violate availability?

## False-positive guards / non-findings
A tag, root user or wide permission is a lead, not automatic exploitability.
Establish the reachable event, actual credential scope and accepted controls.
Inherited protections require evidence; unavailable remote settings remain
unverified rather than presumed missing or effective.

## Evidence requirements
Show the event/input-to-privilege or configuration-to-runtime trace and concrete
consequence. Absence claims state the search universe across reusable workflows,
environment/repository controls and deployment owners. Bind artifact claims to
actual identity; a successful source check does not prove published bytes.

## Exposure metric
Count of pipeline/deploy boundary paths inspected, distinguishing source
configuration from verified external settings and artifact evidence.

## Escalation / cross-lens handoff
Route application dependency trust to secrets-supply and incomplete propagation
to change-closure. Corroborate one root defect when bad artifact trust also
appears as a release-closure issue.

## Out of scope
Changing infrastructure, running jobs, application dependency audits and severity
based solely on a configuration signature.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall