Feasibility

What Is Live

• Route: src/app/(app)/projects/execution/page.tsx
• Route: src/app/(app)/projects/orchestrator/page.tsx
• API route: src/app/api/site/underwrite/route.ts
• API route: src/app/api/site/underwrite/batch/route.ts
• Service: src/lib/feasibility
• Service: src/lib/site-intelligence
• Adapter: src/lib/operator-command/operatorModuleWiringInventory.ts

What Is Not Wired

• Missing critical piece: Canonical boundary between feasibility status, stage state, and decision engine outputs.
• Known risk: Feasibility and Decision Engine can both describe readiness and risk.
• Known drift: Multiple smoke reports compose readiness outside a single source of truth.
• Duplicate logic: Readiness/risk matrices overlap with stage and priority scoring.

Known Blockers

No active blockers are listed.

Next Recommended Action

• Map each feasibility output to exactly one downstream owner: stage, decision, or queue.

System Audit Evidence

• Readiness score: 64%
• Integration depth: operator integrated
• Route exposure: secondary
• Security boundary: partial
• Queue integration: wired
• Readiness integration: wired
• Workflow integration: partial
• Data Room integration: partial
• Export integration: partial
• Test: src/lib/site-intelligence
• Test: src/lib/operator-command/decisions/__tests__/synthesize.dataRoomReadiness.test.ts
• Smoke: scripts/smoke-feasibility-batch-snapshot.ts
• Smoke: scripts/smoke-readiness-risk-matrix.ts
• Persistence: Database-backed projects and tmp smoke reports.

Architecture Governance

• 11 governance doctrines tracked
• 15 required adapter seams
• 13 forbidden direct couplings
• No high or critical governance findings

Capability Registry

• Read-only Feasibility status page for readiness signals and boundary ownership gaps.
• Registry production status: staging
• Primary nav group: Intelligence
• Capability: system audit maturity
• Capability: feasibility evidence inventory
• Capability: source ownership gap
• Capability: safe related links