The repository-evidence feature (--repo-root, meta.repository, node sources) works for architecture and is rejected everywhere else.
$ node bin/archify.mjs validate lifecycle examples/agent-run.lifecycle.json --repo-root .
--repo-root is currently supported for architecture diagrams only.
$ echo $?
2
And meta.repository fails schema validation, since only schemas/architecture.schema.json declares it:
lifecycle schema validation failed:
/meta must NOT have additional properties {"additionalProperty":"repository"}
[schema/additionalProperties] Fix: remove unsupported property "repository".
Why it matters
The authoring-time guard against invented file paths is the most valuable thing about evidence mode, and it is exactly as applicable to the other diagram types:
- a
sequence diagram that names the handler for each message
- a
dataflow node that points at the module producing the events
- a
lifecycle state that cites the function performing the transition
All three want the same revision-verified check, and all three are just as easy for a model to hallucinate as an architecture component's sources.
There is no obvious reason the mechanism could not extend to sequence, dataflow and lifecycle.
Scope note
This is a feature request rather than a bug, and probably a larger piece of work than a small patch: it touches four schemas, the CLI gate, and the evidence-verification path, plus whatever the renderers do to surface evidence in the artifact.
Raising it to find out whether it's wanted before anyone starts.
Verified against main at 19213e1 (v2.13.0).
The repository-evidence feature (
--repo-root,meta.repository, nodesources) works forarchitectureand is rejected everywhere else.And
meta.repositoryfails schema validation, since onlyschemas/architecture.schema.jsondeclares it:Why it matters
The authoring-time guard against invented file paths is the most valuable thing about evidence mode, and it is exactly as applicable to the other diagram types:
sequencediagram that names the handler for each messagedataflownode that points at the module producing the eventslifecyclestate that cites the function performing the transitionAll three want the same revision-verified check, and all three are just as easy for a model to hallucinate as an architecture component's
sources.There is no obvious reason the mechanism could not extend to
sequence,dataflowandlifecycle.Scope note
This is a feature request rather than a bug, and probably a larger piece of work than a small patch: it touches four schemas, the CLI gate, and the evidence-verification path, plus whatever the renderers do to surface evidence in the artifact.
Raising it to find out whether it's wanted before anyone starts.
Verified against
mainat19213e1(v2.13.0).