Align project docs with replay validation scope#216
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the project's documentation and metadata to standardize terminology, shifting from 'replay-integrity' to 'replay-validation' and 'compressed' to 'compact' traces. It clarifies the project's status as a research prototype, explicitly discouraging production-ready framing like 'cognitive fabric,' and adds detailed implementation context for fixtures and the KVTC-V7 prototype. Review feedback focused on maintaining terminology consistency across governance rules and improving the readability of implementation surface lists through better formatting.
|
|
||
| ## Research Alignment Principle | ||
| Every accepted change must strengthen deterministic, offline, reproducible replay-integrity validation for compressed operational traces, or be strictly maintenance-only. | ||
| Every accepted change must strengthen deterministic, offline, reproducible replay validation for compact operational traces, or be strictly maintenance-only. |
There was a problem hiding this comment.
The scope definition here is missing the 'agent/MCP' qualifier used in the canonical positioning (line 4) and research direction (line 16). For consistency in governance documents, the full term should be used.
| Every accepted change must strengthen deterministic, offline, reproducible replay validation for compact operational traces, or be strictly maintenance-only. | |
| Every accepted change must strengthen deterministic, offline, reproducible replay validation for compact operational agent/MCP traces, or be strictly maintenance-only. |
| - audit-oriented | ||
|
|
||
| ## Current Implementation State | ||
| Current implemented surfaces include curated agent trace fixtures in `tests/fixtures/agent_traces/`, the deterministic replay runner in `tests/utils/agent_trace_replay_runner.py`, the MCP replay payload layer in `src/comptext_v7/mcp/`, evidence survival helpers in `src/validation/evidence.py`, replay failure labels in `src/validation/replay_failure_classifier.py`, committed artifacts such as `artifacts/agent_trace_replay_results.json`, and the KVTC-V7 technical-log compression prototype in `src/core/kvtc_v7.py`. |
There was a problem hiding this comment.
This line is extremely long and contains a dense list of file paths. Converting it to a bulleted list would significantly improve readability and align with the formatting used in the 'Strategic State' section above.
| Current implemented surfaces include curated agent trace fixtures in `tests/fixtures/agent_traces/`, the deterministic replay runner in `tests/utils/agent_trace_replay_runner.py`, the MCP replay payload layer in `src/comptext_v7/mcp/`, evidence survival helpers in `src/validation/evidence.py`, replay failure labels in `src/validation/replay_failure_classifier.py`, committed artifacts such as `artifacts/agent_trace_replay_results.json`, and the KVTC-V7 technical-log compression prototype in `src/core/kvtc_v7.py`. | |
| Current implemented surfaces include: | |
| - Curated agent trace fixtures in `tests/fixtures/agent_traces/` | |
| - The deterministic replay runner in `tests/utils/agent_trace_replay_runner.py` | |
| - The MCP replay payload layer in `src/comptext_v7/mcp/` | |
| - Evidence survival helpers in `src/validation/evidence.py` | |
| - Replay failure labels in `src/validation/replay_failure_classifier.py` | |
| - Committed artifacts such as `artifacts/agent_trace_replay_results.json` | |
| - The KVTC-V7 technical-log compression prototype in `src/core/kvtc_v7.py` |
|
|
||
| ## Hard Scope Rule | ||
| A proposal is out of scope unless it directly improves deterministic replay-integrity validation for compressed operational traces without introducing probabilistic or platform-expansion behavior. | ||
| A proposal is out of scope unless it directly improves deterministic replay validation for compact operational traces without introducing probabilistic or platform-expansion behavior. |
There was a problem hiding this comment.
The 'Hard Scope Rule' should use the full canonical term 'compact operational agent/MCP traces' to avoid ambiguity in governance enforcement.
| A proposal is out of scope unless it directly improves deterministic replay validation for compact operational traces without introducing probabilistic or platform-expansion behavior. | |
| A proposal is out of scope unless it directly improves deterministic replay validation for compact operational agent/MCP traces without introducing probabilistic or platform-expansion behavior. |
|
|
||
| ## One-Sentence Rule | ||
| If a change does not directly improve deterministic replay-integrity validation for compressed operational traces, it should not merge into core. | ||
| If a change does not directly improve deterministic replay validation for compact operational traces, it should not merge into core. |
There was a problem hiding this comment.
The 'One-Sentence Rule' is a critical governance boundary and should use the full terminology 'compact operational agent/MCP traces' for precision.
| If a change does not directly improve deterministic replay validation for compact operational traces, it should not merge into core. | |
| If a change does not directly improve deterministic replay validation for compact operational agent/MCP traces, it should not merge into core. |
1 participant
Summary
docs/project_source.md,docs/validation.md, andpyproject.tomlwith the current README positioning from PR Align README with implemented replay validation scope #215Validation
Scope
Documentation/metadata only. No code, tests, fixtures, artifacts, dashboard, or package-lock changes.