e0610c90cd
Sense is the afferent open standard — the always-on, deterministic, energy-accounted record of what is happening around an agent, and a governed account of when that is worth attention. The tool protocols (MCP/A2A/ACP) standardize an agent reaching OUT for capabilities; Sense standardizes the observations flowing IN, the substrate every ambient/ proactive agent needs but none specify. Distinct from OpenTelemetry GenAI: that traces the agent's own reasoning (efferent, non-deterministic by its own admission); Sense records the world the agent is in (afferent), deterministically, every datum provenance- and trust-tagged, every interruption priced in joules and sealed in a receipt. Four tiers, deterministic-first, inference last: - sense-schema — content-addressed Event, vendor-neutral SourceClass, TrustLevel, family Energy/Provenance, StateProjection, Highlight. - sense-store — content-addressed, HLC-ordered, replay-deterministic log; two runs over the same events yield a byte-identical digest. - sense-attention — deterministic salience/novelty/uncertainty observer, k-sigma highlight detector, and the attention budget that gates surfacing by value-vs-interruption-cost (displacement + interference), priced in joules. Perception ⊗ attention-budget — the afferent dual of JCP's capability ⊗ joule-budget. - sense-cascade — query envelope + deterministic recall retrieval + speculative cascade that answers factual recall with zero LLM calls and escalates only as a last resort. - sense-receipt — hash-chained Ed25519 surfacing log (allows AND holds chained); JCR-1 COSE_Sign1 for cross-family verification. SPEC §1-§10, conformance C1-C5 with a reproducible vector pack, a sense-cli end-to-end demo. 38 tests green, clippy clean. Co-Authored-By: Claude Opus 4.8 <[email protected]>
30 lines
1.5 KiB
Markdown
30 lines
1.5 KiB
Markdown
# Sense conformance vectors — v1
|
|
|
|
Reproducible fixtures for the five conformance classes (SPEC §9). A third-party
|
|
implementation is conforming if it reproduces these values from the spec alone.
|
|
Regenerate with:
|
|
|
|
```sh
|
|
cd ../../sense-rs
|
|
cargo run -p sense-conformance --bin sense-gen-vectors
|
|
```
|
|
|
|
- **`meta.json`** — the signing profile: algorithm (EdDSA / COSE `-8`), the
|
|
surfacing-receipt profile tag (`sense/surfacing/1`), the reference steward's
|
|
public key, and its DID. The steward key is a fixed seed everyone has; it
|
|
attests nothing — it only makes the signatures reproducible.
|
|
- **`vectors.json`** — the expected outputs:
|
|
- `c1_replay_digest` — the BLAKE3 replay digest of the scripted event stream.
|
|
- `c2_event_id` — the content id of the canonical event; binds source class and
|
|
trust.
|
|
- `c3_highlights` / `c3_decisions` — the highlights the scripted stream fires and
|
|
the gate's surface/hold decisions.
|
|
- `c4_recall_model` (`deterministic`) / `c4_open_ended_escalated` (`true`) — the
|
|
cascade answered recall with no model call and escalated the open-ended query.
|
|
- `c5_verify_ok` (`3`) / `c5_excision_breaks_at` (`1`) — the surfacing chain
|
|
verifies, and dropping the middle link breaks it at index 1.
|
|
- `c5_first_link_jcr1_envelope_hex` — the first surfacing link as a JCR-1
|
|
COSE_Sign1 envelope, verifiable with the family's shared tooling.
|
|
|
|
The same facts are asserted by the in-repo tests in `sense-conformance`, so the
|
|
published pack and the test suite check identical behaviour.
|