122 lines
3.2 KiB
Markdown
122 lines
3.2 KiB
Markdown
# Skills-Vault Request: M2 Runtime Run Logger And Adapter Manifest Checker
|
|
|
|
Date: 2026-06-20
|
|
|
|
Client repository:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\work-projects\Cognitive-OS-Wantsong
|
|
```
|
|
|
|
Requested supplier repository:
|
|
|
|
```text
|
|
C:\Users\wangq\Documents\Codex\skills-vault
|
|
```
|
|
|
|
## 1. Product Context
|
|
|
|
`Cognitive-OS-Wantsong` will enter M2 after boundary correction.
|
|
|
|
M2 should create product-local runtime adapters and eventually run one minimal manual sample. It must not create canonical CCPE prompt artifacts.
|
|
|
|
This creates a deterministic validation need: adapter files and run records should be checked for authority metadata, manifest completeness, and path consistency without judging model quality.
|
|
|
|
## 2. Repeated Action Or Friction Point
|
|
|
|
Likely repeated checks:
|
|
|
|
- product-local adapter frontmatter includes the required authority fields;
|
|
- no adapter claims canonical CCPE prompt status;
|
|
- run manifest lists all runtime steps and output files;
|
|
- run log paths exist;
|
|
- sample input, internal trace, reader output, and owner note are cross-linked consistently;
|
|
- Local CCRA is not started before the required milestone conditions.
|
|
|
|
These checks are deterministic. They should not become product repo scripts unless the owner explicitly asks.
|
|
|
|
## 3. Proposed Skill Name
|
|
|
|
Candidate name:
|
|
|
|
```text
|
|
cognitive-runtime-manifest-checker
|
|
```
|
|
|
|
Alternative names:
|
|
|
|
```text
|
|
prompt-adapter-boundary-checker
|
|
runtime-run-log-validator
|
|
```
|
|
|
|
## 4. Inputs
|
|
|
|
The Skill should accept:
|
|
|
|
- repository root;
|
|
- optional adapter directory path;
|
|
- optional run directory path;
|
|
- expected authority policy.
|
|
|
|
Expected adapter frontmatter policy:
|
|
|
|
```yaml
|
|
authority: product_local_adapter
|
|
status: draft
|
|
canonical_source: pending_ccpe
|
|
not_canonical_ccpe_prompt: true
|
|
```
|
|
|
|
## 5. Expected Outputs
|
|
|
|
The Skill should produce:
|
|
|
|
- a PASS / FAIL summary;
|
|
- a machine-readable JSON report;
|
|
- finding list with file paths and line numbers when possible.
|
|
|
|
Suggested report fields:
|
|
|
|
```json
|
|
{
|
|
"status": "PASS",
|
|
"adapter_files_scanned": 0,
|
|
"run_files_scanned": 0,
|
|
"blocking_findings": [],
|
|
"warnings": []
|
|
}
|
|
```
|
|
|
|
## 6. Safety Boundaries
|
|
|
|
- Read-only by default.
|
|
- No content generation.
|
|
- No prompt rewriting.
|
|
- No model-quality judgment.
|
|
- No Local CCRA judgment.
|
|
- No file edits unless a future explicit `--write-report` option is requested.
|
|
|
|
## 7. Validation Expectation
|
|
|
|
Minimum validation cases:
|
|
|
|
- adapter with correct frontmatter passes;
|
|
- adapter missing `not_canonical_ccpe_prompt: true` fails;
|
|
- adapter claiming `authority: ccpe_canonical` fails inside the product repo;
|
|
- missing run output path fails;
|
|
- Local CCRA directory present before the allowed milestone warns or fails according to config;
|
|
- JSON report is stable and machine-readable.
|
|
|
|
## 8. Why This Should Become Reusable Automation
|
|
|
|
The operation is deterministic metadata and manifest checking. It does not depend on QPI content quality or Intellectual Archaeology reasoning.
|
|
|
|
It is likely reusable for other product repos that consume CCPE canonical prompt contracts while keeping product-local adapters separate.
|
|
|
|
## 9. Current Blocked Task
|
|
|
|
This is not blocking M2a boundary correction.
|
|
|
|
It may become useful before M2b manual sample execution, especially if multiple adapter and run files are created.
|