CLARIXO Continuity Integration Manual

Integration Philosophy

• Observe-only
• Non-blocking
• Runtime-neutral
• Append-oriented
• Governance-visible

Current Action Route

/?action=continuity-agent-action

This route supports continuity thread creation, append operations, latest snapshot reads, filtering, upstream reference attachment, and continuity history preservation.

Minimal Runtime Flow

User Interaction
  ↓
AI Runtime Generates Output
  ↓
Evidence Record Written
  ↓
Responsibility Attribution
  ↓
Continuity Observation Written
  ↓
Runtime Observation Surface Updated

HIC Runtime Flow

User hesitation, uncertainty, overload, pacing request, or pause boundary
  ↓
Continuity admissibility detection
  ↓
Bridge routing
  ↓
Continuity runtime activation
  ↓
Paced guidance
  ↓
Runtime observability

HIC Runtime must be integrated before generic model fallthrough can absorb continuity-relevant interaction states.

Runtime Observability Markers

• hic_fallthrough_force_clarixo
• clarixo_gate
• clarixo_general_payload
• clarixo_general_inline_done
• continuity_agent
• continuity.guidance

These markers make continuity governance attributable, debuggable, and distinguishable from ordinary model tone.

Production Integration Lessons

• Governance interception must happen before generic OpenAI or model fallthrough.
• Runtime authority family must remain separate from runtime subtype.
• Human hesitation is a runtime governance condition, not merely a prompt variation.
• Continuity governance requires runtime observability to remain attributable and debuggable.
• Bounded governance is critical to avoid continuity overreach.

Authority Hierarchy Rule

{
  "source": "clarixo",
  "runtime_source": "clarixo_continuity"
}

Use source for the authority family and runtime_source for the runtime subtype. Do not replace source with the subtype.

Latest Snapshot Read

/?action=continuity-agent-action&latest=1&limit=20

Minimal Continuity Object

{
  "runtime_source": "tgtracing",
  "continuity_state": "observable",
  "review_required": false,
  "transfer_state": "observation_only_not_transferred",
  "boundary_conditions": [
    "observe_only_no_runtime_blocking",
    "runtime_response_already_generated_before_continuity_write"
  ]
}

Observation Categories

• observable
• warning
• degraded
• review_required
• restricted_transfer
• restoration_observed
• continuity_mismatch
• admissibility_observation_only

Upstream Governance Binding

{
  "upstream_reference": {
    "evidence_id": "evi_example",
    "responsibility_object_id": "l2_obj_example",
    "preserves_upstream_boundary": true
  }
}

Attached references preserve governance lineage. They do not automatically inherit downstream authority.

TGTRACING Integration Example

TGTRACING currently demonstrates Runtime Continuity Observation with observe-only boundaries, including no runtime blocking, no business-logic modification, and continuity writes after runtime response generation.

Closing Integration Statement

The CLARIXO Continuity layer preserves runtime governance continuity visibility across time while keeping execution authority separate.