Repository navigation
Add sourced Autopilot plans and attributed formation handoff - #11
Merged
Merged
Conversation
added 9 commits
October 25, 2026 17:28
Broad annual-report, tax-registration and local-license hits prove provenance, not relevance to the founder plan. Keep retrieval in the tool trace, but omit all such records from sources and item bindings, remove the first-tax full-text promotion, retain reviewed guides/catalog duties and exact local coverage, and state the unverified-law gaps explicitly. Regression first reproduced four unrelated source bindings from education, insurance, aircraft and local-license fixtures. Correct the prior hosted alcohol-law expectation. Validation: npm test (144 Autopilot and 6 MCP tests plus plugin drift), npm run build, npm run typecheck, git diff --check.
Address approved review LOW-2: the opening warning no longer suggests search matches are displayed. Keep the reviewed diagnostic calls and existing guard comment in this patch. Follow-up suggestion: remove diagnostic-only broad searches after separately reviewing tool-trace and deadline behavior.
Record approved FC source cb3999b, its deployed checksum and narrow backend smoke, plus live web source/deployment. Keep email false and final postchecks and pilot validation pending. Correct directly affected README claims about plan law sources and distinguish optional plan ordering from legacy chat routing. No code or deployment changes.
Record deployed resume/delete endpoints and passing public fake-token smoke, disabled email status and new sending, and registered cleanup cron with scheduled success still pending. Documentation correction only.
teakesdev
marked this pull request as ready for review
October 26, 2026 05:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Formation Autopilot returns structured founder plans with guide/catalog sources, guided inputs, complete live quote qualifiers and a hosted formation handoff that carries campaign attribution. Qwen orders known steps; it cannot author displayed obligations or source records. Existing chat and spending limits are preserved.
Broad annual-report, tax and local keyword matches are withheld from plan sources because matching a jurisdiction does not establish relevance. Plans retain explicit unresolved-requirement warnings, exact city coverage facts and diagnostic tool traces. This prevents unrelated education, insurance, aircraft and licensing laws from appearing as support for a founder’s steps. Slow upstream calls still degrade within the overall deadline.
Validation at cb3999b: 144 Autopilot tests and 6 MCP tests passed without skips; build, typecheck and fixture/skill drift checks passed. A regression first reproduced four irrelevant law bindings and now excludes them from the entire plan response. Opus 5.5 approved the mitigation; its warning-copy correction is included. Production consumer smoke remains part of rollout verification.
Draft integration PR. Ty approved the production rollout separately: FC code was deployed without environment/capacity changes, and the matching Corpus web release is live with email disabled. Email requires the remaining production checks; no purchase or filing was made. Deployment receipts live in the Corpus repository’s Autopilot production release runbook and daily ledger.