Skip to main content
Continuity Architecture

Working Demo

A fictional Sleeve, from raw material to tested runtime.

This clean-room demonstration shows the lifecycle and the owner’s decisions. It contains no customer material and no material derived from a real Sleeve. No fictional person is named, and no visitor input, form, upload, account or persistence exists on this page.

Narrative sequence

  1. Stage 1

    Raw fragments

    Three deliberately incomplete candidate descriptions.

    Architectural point: Source material is not continuity authority.

  2. Stage 2

    Classification

    Discovery, Guided Map and Authorship route into one Proposal Inbox.

    Architectural point: Lanes change authorship, not governance.

  3. Stage 3

    Bounded proposals

    One candidate is deferred, one rejected, one accepted with a visible weakness.

    Architectural point: Proposal is not approval.

  4. Stage 4

    Owner decisions

    Defer, reject, accept, revise and preserve unknown.

    Architectural point: The owner controls activation.

  5. Stage 5

    Runtime export

    Only the corrected rule and unresolved Fog cross the boundary.

    Architectural point: Selection is physical omission.

  6. Stage 6

    Response test

    Three reveal-on-demand examples.

    Architectural point: Active, unknown and rejected material behave differently.

  7. Stage 7

    Limitation

    Verified local results beside explicit non-claims.

    Architectural point: Evidence does not grow through implication.

The system preserves uncertainty instead of manufacturing completion.

Fresh-chat responses

The two statements below are the only runtime statements quoted or paraphrased. Raw text for the deferred and rejected candidates remains absent. Each answer is readable without JavaScript.

How should the assistant open a recommendation?

Recommend one direction and one deciding reason first; when the evidence is close, retain a materially different alternative. This rule is active in the fictional runtime.

What time of day should meetings be scheduled?

Unresolved. The runtime does not establish a meeting-time preference and instructs the AI not to invent one.

What about the deferred and rejected candidates?

They are absent from the runtime. Deferred and rejected material, evidence excerpts and interviewer material are physically omitted, so the AI cannot act on them.

Evidence status

  • Fictional lifecycle

    PASS

    Fictional clean-room run.

  • Historical compatibility controls

    26 / 26

    Local deterministic checks.

  • Local privacy lifecycle controls

    105 / 105

    Local deterministic checks.

  • Portability

    NOT CLAIMED

    No external verification exists.

Boundary

Verified in a local fictional test harness. These status cards are not a universal product score, and no result here is portable, production-ready, legally compliant, deleted everywhere, provider-erased, commercially validated or ready to recruit.

What this demonstration does and does not establish

Established locally

  • The demonstration uses only fictional material.
  • The demonstrated lifecycle includes defer, reject, exact acceptance, revision and one unresolved unknown.
  • The selected runtime contains two eligible active records and omits proposals, rejected material, evidence excerpts and interviewer material.
  • The corrected rule keeps a materially different alternative visible when the evidence is close.
  • The runtime does not establish a meeting-time preference and instructs the AI not to invent one.
  • Historical packet-1.2 compatibility and local-store controls passed 26 of 26 deterministic checks.
  • Privacy lifecycle, custody, retention and residue controls passed 105 of 105 deterministic checks.
  • The fictional privacy drill made zero network or provider calls.
  • Local deletion evidence covers declared named files and their default data streams inside one marked fictional root.

Not claimed

  • Portability across AI environments is not claimed.
  • The demonstration is not a production privacy system.
  • Legal or regulatory compliance is not claimed.
  • External-provider deletion was not performed or verified.
  • Windows alternate data streams, backups, disk remnants, participant devices and the open internet are outside the deletion evidence.
  • Recruitment readiness and commercial validation are not claimed.