audit is silent about pre-v1 memory envelopes, which then fail at projection time #43

New issue

Open

opened 2026-08-02 07:03:23 +00:00 by PerishFire · 0 comments

PerishFire commented

2026-08-02 07:03:23 +00:00

Owner

Environment: concord v0.9.0.

Observed

Three of the tasks in the current domain space carry pre-v1 MAIN.md. audit --json reports nothing for any of them:

perish.code/posta-cold-start                 legacy | faults=0 observations=['boundary']
perish.code/infra-desired-state-cli          legacy | faults=0 observations=[]
powerformer.net/feat-windows-odeval-node     legacy | faults=0 observations=[]

The problem surfaces only when a projection is attempted, mid-operation:

$ concord memory read perish.code/posta-cold-start --section focus
concord: section projection requires concord-memory:v1

That is the point at which an agent has to abandon memory patch and fall back to whole-file memory write, which is both more dangerous and more expensive.

The information already exists

memory phase list --json returns a structured field per phase:

{"number": 0, "path": ".../PHASE-00.md", "revision": "4591bc6e...", "structured": false}

audit --json has no equivalent for MAIN.md, and its observations[] never mentions the envelope version.

Proposal

Emit a non-gating memory observation when MAIN.md is not concord-memory:v1, and add structured to the audit JSON memory node.

The skill's Standing list already claims "memory schema and limit hygiene in audit". Envelope version is not covered by that today, so either the check or the claim should move.

Environment: concord v0.9.0. ## Observed Three of the tasks in the current domain space carry pre-v1 `MAIN.md`. `audit --json` reports nothing for any of them: ``` perish.code/posta-cold-start legacy | faults=0 observations=['boundary'] perish.code/infra-desired-state-cli legacy | faults=0 observations=[] powerformer.net/feat-windows-odeval-node legacy | faults=0 observations=[] ``` The problem surfaces only when a projection is attempted, mid-operation: ``` $ concord memory read perish.code/posta-cold-start --section focus concord: section projection requires concord-memory:v1 ``` That is the point at which an agent has to abandon `memory patch` and fall back to whole-file `memory write`, which is both more dangerous and more expensive. ## The information already exists `memory phase list --json` returns a `structured` field per phase: ```json {"number": 0, "path": ".../PHASE-00.md", "revision": "4591bc6e...", "structured": false} ``` `audit --json` has no equivalent for `MAIN.md`, and its `observations[]` never mentions the envelope version. ## Proposal Emit a non-gating memory observation when `MAIN.md` is not `concord-memory:v1`, and add `structured` to the audit JSON memory node. The skill's Standing list already claims "memory schema and limit hygiene in audit". Envelope version is not covered by that today, so either the check or the claim should move.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

PerishFire/concord#43

No description provided.

Rows
Columns