if.trace

Protocol module

if.story

Narrative logging (vector vs bitmap): keep a compact “why” trail so a future operator can re-derive the decision, not just read a status update.

Status (black/white): if.story is preview only on this host (no deployed runtime). Example artifacts are published for review.

Design target: when an output matters, bind published artifacts to if.trace so third parties can verify the bytes without accounts.

Open protocol pack (HTML) Open demo artifacts (HTML) Lint rules How verification works See if.gov
Black / white
What it gives you
  • A multi-resolution narrative (signal / punch / full) plus an explicit “trap” for future maintainers.
  • A machine-readable metadata companion for linting and indexing.
What it does not claim
  • No proof of factual correctness, safety, or intent.
  • No deployed runtime or performance guarantees on this host.

Protocol (v1 shape)

A dual-format artifact: fast bitmap metrics plus a vector narrative that preserves the “why”.

Bitmap
Counters and status snapshots (latency, backlog, incidents, costs).
Vector
Narrative logging: constraints, options considered, why rejected, and a “trap” that prevents regressions.

Where it fits

A protocol used by outputs like if.gov and high-stakes controls on if.bus/if.api.

Event
A decision, incident, or control action that needs memory.
if.story
Emit narrative + metadata (+ optional receipts).
Review
Humans and tools can re-derive the decision path later.
contact