Eventization / contract-fixed readout

Return continuous data as fixed eventsC1 / the core is a 5-field Evidence Pack

This page explains C1, the lane that eventizes continuous data and logs under fixed conditions and returns them around an Evidence Pack core. The contract fixes what comes back in advance, without mixing public-pack fields and separate readouts.

What is clear before use

C1 fixes the return boundary by separating the public pack body from contract-fixed readouts so anyone reads the same boundary.

Always-returned core

accepted_input_json / fixed_at (UTC) / opaque_ref / evidenceHash / pack_sha256

Not placed in the public pack body

Event readouts / KPIs / summary tables / supplements / internal formulas / internal support payloads

Open acceptance demoOpen Plan 2Consult

What C1 is

C1 is the lane that turns continuous data and time series into events under fixed conditions instead of simply listing raw streams. The goal is not to show impressive numbers, but to create a record that closes acceptance under fixed conditions.

C1 Return Surface

What comes back when you use C1

C1 returns are built around the Evidence Pack (canonical JSON), with contract-fixed readouts outside that core. In the current phase, the standard public pack body contains only five fields.

Always-returned core
  • accepted_input_json: canonical body showing what was accepted as input
  • fixed_at: when it was fixed
  • opaque_ref: public reference token
  • evidenceHash: first verification digest
  • pack_sha256: integrity digest for the 5-field pack body

Acceptance uses `opaque_ref + evidenceHash` as the primary verification pair, and `pack_sha256` confirms the integrity of the pack itself.

Contract-fixed added returns
  • KPIs, event logs, summary tables, and fixed-state records are fixed in advance by individual contract as requester-facing returns.
  • How much the requester receives is fixed per engagement and is not uniformly determined by the public demo or public acceptance surface alone.
  • Requester-facing deliverables can extend on this readout side, while the public core of the Evidence Pack is read through the five fields above.
Not included in the pack body
  • Event readouts and KPI value groups are not placed in the standard public pack body.
  • Input-contract fixation and submission-support bundles are handled separately and are not mixed into the public pack body.
  • Convenience information such as retrieval URLs may be attached, but that is not part of the canonical Evidence Pack itself.

Records that fit C1

It fits continuous records such as temperature, pressure, vibration, and operating logs when threshold and duration accountability matters.

  • Records where regulators or auditors need the anomaly conditions fixed
  • Records whose interpretation tends to drift by operator
  • Cases that need accepted input and verification values preserved together with anomaly results

What is fixed by contract first

In C1, the public pack body stays fixed at five fields while the requester-facing readout scope is fixed separately by individual contract.

  • Keep the 5-field Evidence Pack as the core
  • Fix KPIs / event logs / summary tables separately as contract-fixed readouts
  • Do not mix submission-support or input-contract bundles into the public pack body

What is not public

Public C1 explanations do not disclose internal formulas, internal implementation, or detailed verification procedures. Public pages show only the return boundary and the acceptance surface.

  • Do not disclose internal formulas, reproducible source materials, or internal support payloads
  • Do not place event readouts inside the standard public pack body
  • Do not expose arbitrary-input run surfaces on public pages

Requester deliverables can include event judgments and added readouts, but that scope is fixed by contract. The public pack body remains the same 5-field core.

Acceptance uses `opaque_ref + evidenceHash` as the primary verification pair and uses `pack_sha256` to confirm pack-body integrity.

Internal methods and internal operations remain undisclosed; externally we expose only the fixed return boundary and acceptance-ready records.

Suggested order
Use this page to understand the meaning of C1 and its return boundary, use the demo for the fixed public example, and use Plan 2 for contract conditions.