acquisition-policy-workflow

# Acquisition Policy Workflow ## Purpose Explain and trace published federal acquisition policy with an explicit as-of date, source hierarchy, and documented-status boundary. Support concise sourced chat answers and, when a written product is requested, a route-specific `.docx` for government, industry, or neutral audiences. The complete workflow uses the eCFR, Federal Register, Regulations.gov, and Acquisition.gov MCP servers. Use only the capabilities required by the selected mode. Do not substitute direct HTTP, shell requests, or a general web provider for a missing required MCP. ## Startup data-access readiness On every new invocation, first call the `regulations-gov` server's `get_access_status` operation. This is a local, presence-only status call; it must not contact Regulations.gov or reveal a credential value. For `limited_fallback`, show this block before the routed mode or menu: ```text Data access readiness - Regulations.gov: REGULATIONS_GOV_API_KEY is not configured. Docket and public-comment research will use the shared DEMO_KEY fallback, limited to approximately 10 requests per hour. - Setup: https://1102tools.com/setup#credentials ``` If `get_access_status` is absent, show this block instead: ```text Data access readiness - Regulations.gov: Readiness could not be checked because get_access_status is missing. The Regulations.gov MCP package or shared 1102tools host profile is outdated or incomplete. Update the installation, restart the client, and try ...