Which specification are you working?
Pick the document. Its requirements carry through to the crosswalk, so the ledger opens already scoped to what you selected here.
Which of its requirements does the authority actually require?
The ledger. Every requirement in scope, its proposed disposition, its citations, and the confirm/override control.
Across the portfolio, what does this free up?
The figure the memo needs, with every driver visible and editable.
Where does the removable burden sit?
The same numbers grouped by organization, with retained categories shown as locked context.
How the agent works (and its limits)
Three cooperating agents share one knowledge base. The crosswalk agent retrieves the governing authority for each specification requirement and proposes a disposition — commercial / adaptable / unique — with a confidence score, a short rationale, and citations. Every call is agent-proposed; The contracting officer and program manager preparing the specification, with the Portfolio Acquisition Executive reviewing the rollup. confirms or overrides, and that determination is what the summary reflects.
The specification-review agent takes one specification's specification requirement set and reports what changes and how much burden hours that frees. The impact model prices it from drivers you can edit on screen.
Architecture. A FastAPI backend puts the reasoning model behind one swappable interface (Anthropic Claude via Bedrock in cloud/GovCloud; an open-weight model on vLLM/Ollama for air-gapped enclaves; a deterministic mock for offline demos) and retrieval behind another (pgvector on Postgres in production; in-memory lexical for the demo). The frontend is dependency-free static files and does not know which is live.
Limits. These classifications are judgements the responsible official owns: the agent accelerates the analysis, it does not replace them or any approval process. TODO — state this domain's specific limits here.