[codex] Close out SEC proof narrative#84
Merged
Conversation
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.
Summary
This closes out the current SEC proof narrative and makes the generated evidence easier to understand without a narrated walkthrough.
Key changes:
flywheel-memorysubprocess session instead of spawning once per notecandidate-noise.mdreport explaining why 31 staged candidates are not active review workWhy
The visible SEC review queue is now clear, but the reports still showed staged candidate counts without explaining why those candidates were not review events. That made the product loop look unfinished or inconsistent.
This PR makes the distinction explicit: the active human review queue is empty, while 31 staged candidates are suppressed because they are duplicate pressure on already-refuted assumptions. That keeps the audit trail visible without asking reviewers to re-adjudicate the same failed assumptions.
The writer change also removes a practical scaling problem: generated report bundles no longer pay subprocess startup cost per Markdown page.
Evidence paths
evidence/sec-company-ledgers/sec-10y-100-company/reports/company-runs/sec-10y-100-company/index.mdevidence/sec-company-ledgers/sec-10y-100-company/reports/company-runs/sec-10y-100-company/dashboard.mdevidence/sec-company-ledgers/sec-10y-100-company/reports/company-runs/sec-10y-100-company/proof-path.mdevidence/sec-company-ledgers/sec-10y-100-company/reports/company-runs/sec-10y-100-company/review-queue.mdevidence/sec-company-ledgers/sec-10y-100-company/reports/company-runs/sec-10y-100-company/candidate-noise.mdValidation
npm run build -w @velvetmonkey/flywheel-ideas-corenpm run lint -w @velvetmonkey/flywheel-ideas-corenpm test -w @velvetmonkey/flywheel-ideas-core -- write-subprocess write-dispatchernpm test -w @velvetmonkey/flywheel-ideas-core -- company-trackernpm test -w @velvetmonkey/flywheel-ideas-coremcp-subprocess:write_path=mcp-subprocess reason=subprocess_ok,exported_markdown=3606No SQLite, JSON, JSONL, WAL/SHM, or raw SEC cache artifacts are included.