LABSPUBLIC RESEARCH INSTITUTE
← Instrument galleryD03-GLYPHCAS-IDENTITY-EXPLORER

GlyphCAS Identity Explorer

A deterministic browser-local research instrument.

Related paperBenchmark contract
DETERMINISTIC FIXTURE · NOT A PERFORMANCE RESULT

GlyphCAS Identity Explorer

MECHANISMTyped exact, semantic, contextual, and representation identities
AUTHORITYSHA-256 ContentId remains sovereign
COMMIT RULEReuse requires an explicit equivalence contract and current dependencies.
FAIL-CLOSED RULEApproximate similarity never promotes itself to exact identity.
STATEEXACT_HITf792856c
ContentId0
context keyEXACT_HIT
reuse verdictf792856c
  1. EXACT_HIT
  2. SEMANTIC_ALIAS
  3. APPROXIMATE_CANDIDATE
  4. REUSE_ALLOWED
  5. REUSE_DENIED
  6. INVALIDATED
CONTRACT CONTROLS

Each control executes a declared browser-local transition. Repeated dual-outcome controls alternate deterministically.

FIXTURE ASSERTIONS

NOT YET EXERCISEDOne-byte change changes exact ContentId.

NOT YET EXERCISEDProject or authority change breaks contextual reuse.

NOT YET EXERCISEDDependency invalidation preserves immutable exact blobs.

NOT YET EXERCISEDApproximate candidates never become exact identity.

RECEIPTED EVENT LOG

No transition yet. Operate a declared control.

This transparent browser-local instrument teaches the authored state contract. Exercising an assertion demonstrates fixture behavior only; it is not evidence of production performance, compression ratio, model uplift, cognition, safety, or universal correctness.

Purpose

Show why exact content, logical object, semantic class, contextual reuse, dependency, representation, spatial, and receipt identities must remain separate.

Mechanism

Users edit bytes, paraphrase meaning, change project or authority scope, change a dependency, encode a new representation, and move a card. The explorer highlights exactly which IDs must change and which remain.

Deterministic fixture

Two paraphrases of a bounded authentication rule, two projects, two authority scopes, three dependencies, and P/D representation candidates.

The fixture must live in content/demos/d03-glyphcas-identity-explorer/fixture.json, validate before the demo renders, and be resettable without a network call. A future live adapter may be added behind a visibly separate mode.

Required controls

  • Edit one byte
  • Paraphrase
  • Switch project
  • Switch authority
  • Change policy version
  • Invalidate dependency
  • Encode representation
  • Move spatial card
  • Attempt illegal semantic promotion

Visible states

  • EXACT_HIT
  • SEMANTIC_ALIAS
  • APPROXIMATE_CANDIDATE
  • REUSE_ALLOWED
  • REUSE_DENIED
  • INVALIDATED

Every state must have text, iconography, and a non-color-only distinction. State transitions are logged in an in-memory demo receipt visible in the inspector.

Core assertions

  1. One-byte change changes exact ContentId.
  2. Project or authority change breaks contextual reuse.
  3. Dependency invalidation preserves immutable exact blobs.
  4. Approximate candidates never become exact identity.

Layout

The page contains:

  1. a concise mechanism explanation;
  2. the interactive stage;
  3. a state and evidence inspector;
  4. a reset control;
  5. a “what this proves / what it does not prove” panel;
  6. links to the related paper and benchmark contract.

On narrow screens the inspector becomes a bottom sheet. The stage must remain usable at 360 CSS pixels.

Accessibility

  • All operations are keyboard reachable.
  • Pointer gestures have button or keyboard equivalents.
  • Animated transitions honor prefers-reduced-motion.
  • Focus remains visible and returns predictably after sheets close.
  • Diagrams expose concise text alternatives.
  • Status is announced through a polite live region only when the user initiates the transition.

Instrumentation

Record locally:

demo_id
fixture_version
action
prior_state
result_state
validation_result
timestamp_relative

Do not send telemetry. Provide “Export demo trace” as JSON for debugging and reproducibility.

Automated tests

  • fixture schema validation;
  • deterministic reset;
  • every required control transition;
  • every assertion above;
  • invalid and stale fixture handling;
  • keyboard path;
  • 360 px and 1440 px screenshots;
  • zero critical console errors;
  • no request to a paid API in default mode.

Publication boundary

Semantic equivalence is demonstrated only for declared fixtures under an explicit contract.

The interface must never convert illustrative values into a benchmark claim. A measured result appears only when linked to a versioned run receipt.