Shared Schemas

The shared schema directory is the coupling surface between tools.

Schema	Produced by	Consumed by	Purpose
transcript.schema.json	Seam	meshmapper, Assay	Hash-chained record of captured messages and rewrites.
path-hypothesis.schema.json	meshmapper	Assay M5-lite binding	Candidate attack path, explicitly proven: false.
finding.schema.json	Assay, aipostex	reporting	Proof-carrying finding with oracle evidence, trial stats, and transcript refs.

Validate artifacts on write and on read.

Transcripts

Transcripts contain records[]. Each record has a before message, optional after message, rule_applied, prev_hash, and hash.

Seam writes them. meshmapper uses them as observed graph evidence. Assay stores returned transcript hashes in findings.

Path Hypotheses

Path hypotheses include class, entry, target, hops, trust_basis_gaps, taxonomy tags, rationale, graph_ref, and proven: false.

meshmapper emits them to tell an operator where to test. They are not evidence by themselves; Assay can attach one through an explicit binding file before proving the side effect with an oracle.

Findings

Findings include intent, method, evidence, stats, and transcript_refs.

Assay findings should cite an oracle-observed side effect. Agent narration does not satisfy the schema's evidence intent, even if it is present in a transcript.