teleo/teleo-infrastructure
8
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions 1
teleo-infrastructure/docs/phase1b
History
twentyOne2x cdb0b1498d Add phase 1b local review guide
2026-05-29 14:17:28 +02:00
..
agent-identity-router-spec.md Implement phase 1b agent routing 2026-05-29 14:00:13 +02:00
eval-pipeline-integration-spec.md Harden local phase 1b review path 2026-05-29 14:16:12 +02:00
github-identity-bot-posture-spec.md Implement phase 1b agent routing 2026-05-29 14:00:13 +02:00
local-review-guide.md Add phase 1b local review guide 2026-05-29 14:17:28 +02:00
README.md Record phase 1b staging blocker 2026-05-29 14:01:21 +02:00
reporting-contributor-compatibility-spec.md Implement phase 1b agent routing 2026-05-29 14:00:13 +02:00
staging-blocker.json Record phase 1b staging blocker 2026-05-29 14:01:21 +02:00
staging-proof-spec.md Implement phase 1b agent routing 2026-05-29 14:00:13 +02:00

README.md

Phase 1b Spec Index

Status: active draft Parent spec: docs/phase1b-agent-routing-spec.md

Scope

Phase 1b is the decision-engine PR evaluation router. It sends each KB mutation to the owning Hermes agent identity, supports top-2 cross-domain review, posts parseable VERDICT:AGENT:* comments through one master bot account, preserves existing merge or feedback behavior, and proves the change in staging before production cutover.

Specs

Workstream Spec Implementation posture
Agent identity router docs/phase1b/agent-identity-router-spec.md ready_now
Eval pipeline integration docs/phase1b/eval-pipeline-integration-spec.md ready_now after router contract freezes
GitHub identity and bot comments docs/phase1b/github-identity-bot-posture-spec.md ready_now after canonical target config freezes
Reporting and contributor compatibility docs/phase1b/reporting-contributor-compatibility-spec.md ready_now after verdict state shape freezes
Staging proof docs/phase1b/staging-proof-spec.md draft_gated on staging/VPS or disposable remote access
Staging blocker docs/phase1b/staging-blocker.json external_only

Execution Order

  1. Implement router contract and tests.
  2. Wire eval pipeline to required reviewer agents under a feature flag.
  3. Route comments through the canonical GitHub target with idempotency markers.
  4. Update reporting and contributor accounting to read reviewer sets rather than fixed Leo plus domain slots.
  5. Run staging proof on a clone or disposable remote target before production cutover.

Claim Boundary

These specs plus the Phase 1b branch prove only local implementation behavior. A production completion claim requires merged code, passing tests, staging proof, exact production SHA deployment, Leo signoff, and 24-hour production daemon stability.