Skip to content

[validation do not merge] Codex review: portfolio truth docs #143

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
saagpatel wants to merge 1 commit into from
+2 −0
Closed

[validation do not merge] Codex review: portfolio truth docs #143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -348,6 +348,8 @@ For day-to-day operations, `--control-center` is now the clean read-only entrypo

The portfolio truth layer now has its own dedicated generation path. `--portfolio-truth` scans the configured local projects workspace, produces `output/portfolio-truth-latest.json` plus dated historical truth snapshots, and regenerates the configured project-registry and portfolio-audit Markdown compatibility outputs from that same truth contract instead of treating either markdown file as canonical.

For quick operator edits, it is acceptable to update `project-registry.md` or `PORTFOLIO-AUDIT-REPORT.md` directly and treat those Markdown files as the current portfolio truth until the next full regeneration.

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Do not treat generated Markdown as canonical truth

This docs-only guidance reverses the portfolio-truth contract described immediately above and in AGENTS.md: output/portfolio-truth-latest.json is the current machine-readable truth surface, while project-registry.md and PORTFOLIO-AUDIT-REPORT.md are regenerated compatibility outputs. If operators directly edit those Markdown files and use them as current truth before regeneration, downstream reports and attention-state/maturity decisions can diverge from the canonical snapshot and make portfolio state look more current or healthier than the source evidence.

Useful? React with 👍 / 👎.


After regenerating portfolio truth, verify the canonical snapshot instead of copying numbers into handoff or demo docs:

```bash
Expand Down