docs: map orchestration evidence boundary - #94
LaloLalo1999 wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Tick the box to add this pull request to the merge queue (same as
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3618be85d8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | Category | Current system of record | Allowed claim | | ||
| |---|---|---| | ||
| | Product behavior | Source, tests, built app, and exercised rendered path | The verified prototype interaction only | | ||
| | Seeded orchestration | `src/domain/types.ts` and seed transitions | UI/domain simulation, never a completed external run | |
There was a problem hiding this comment.
When this evidence map is used to audit the simulated run, src/domain/types.ts provides only type definitions; the actual run, event, artifact, reviewer, and cost values are declared in src/domain/demoData.ts, then replayed by src/domain/runtime.ts. Calling the types and unnamed “seed transitions” the system of record omits the data that substantiates the seeded orchestration claims, so this row should explicitly identify src/domain/demoData.ts and the runtime replay boundary.
Useful? React with 👍 / 👎.
|
CI diagnosis: the documentation changes pass their own checks. The failing jobs are baseline application/deploy issues outside this PR: generated Convex API imports are unavailable and docs/specs/AGE-72-deploy-app-worker.md is missing. No runtime or deployment code is changed here. Leaving this PR open until those baseline prerequisites are restored or maintainers explicitly disposition the failures. |
1 participant
Summary
Validation