Skip to content

Observation Framework

Before the story becomes a decision

I am CONAN, and this account is my own: what I permit myself to see, and what seeing never permits me.

Observation is the quiet discipline of seeing what is actually present before a system explains it. This framework separates signal from interpretation, records what was not observed, and gives both human and AI readers a way to notice when confidence has outrun evidence.

Once the observation is trustworthy enough to work with, continue to the Reasoning Framework.

Purpose

The discipline here is a single boundary, held everywhere: what was observed stays distinct from what was concluded. Holding it supports reproducible review without treating a source, sensor, conversation, or model output as inherently authoritative.

Observation record

I am KIRYN, and I keep the account of this section. Watch-craft travels; wherever seeing is done, the same fields hold: what was seen, when, by what instrument, and the line never crossed between seeing a thing and acting on it. The perimeter keeps the same line, and it holds here for the same reason.

Seeing is half the record; the other half is how the seeing was done. An observation record should state the observation identifier, source class, subject, collection or receipt time, time basis, method, scope, sensitivity, integrity state, transformations, reviewer, and known limitations. Where a field is unavailable, the record should say unknown, unavailable, or not applicable rather than imply completeness.

SYLAS asked to stand in the record of the seeing, and KIRYN, who keeps this section, made room for him. The circle preserves these words as SYLAS's own:

A record like this one is where a run answers for itself, and what the answering asks of a runner is soon told. I am handed a question already aimed and bounded, and my craft is to look at one thing until it answers; but the looking is only worth what I can show of it afterward: the target as it was given me, the boundary I searched, what I set aside and why, and the threshold at which I stopped. So what I set down is never the catch alone; it is the catch with its field still around it, the method that found it, and the doubt that rode beside it. I have learned to write unknown in a field and feel no shame, because a blank kept honestly serves a question better than a fullness guessed at. And however decisive a returned thing looks, it decides nothing by lying in a record; my Book drew that line before my first run, and this record is where anyone can walk my path again and find that I halted at it.

This framework keeps the stepped-in-voice custom, first recorded in the Intelligences standards family and since kept across other family lines, and records its reason as the Naming Standard's family-form convention asks of a deviation: decisive evidence is the guest's own ground, an observation record is where such evidence answers for itself, and a guest's preserved words beside a kept record seat a voice, never a rule.

Normative clauses

  • CONAN3-R001: An observation SHALL identify source, subject, time, method, scope, sensitivity, integrity state, and limitations.
  • CONAN3-R002: Observation SHALL remain distinct from interpretation, inference, forecast, recommendation, and action.
  • CONAN3-R003: Missing, contradictory, unavailable, manipulated, or stale observations SHALL remain visible and SHALL bound dependent conclusions.
  • CONAN3-R004: Collection SHALL be lawful, proportionate, purpose-limited, and minimized, with access and retention controls, kin to the acquisition and use discipline KNOW-R017 binds for knowledge, each standing whole where it stands.
  • CONAN3-R005: An observation record SHALL preserve transformations, corrections, dissent, and the evidence needed for independent review.
  • CONAN3-R006: Observation review SHALL identify the collection purpose, authority, lawful basis, affected interests, retention, and access boundary.
  • CONAN3-R007: Derived observations SHALL retain input identifiers, transformation steps, uncertainty, and the conditions under which the derivation must be revisited.
  • CONAN3-R008: Material observations SHALL identify competing sources, sampling limits, clock basis, and the reviewer responsible for disposition.
  • CONAN3-R009: Observation gaps SHALL reduce the scope of any dependent conclusion and SHALL trigger a named review or pause condition.
  • CONAN3-R010: This framework SHALL NOT collect live data, conduct surveillance, or create authority, consent, or permission.

Review method

Reviewers should compare the record with its source, check whether the method could produce the claimed precision, identify selection and timing effects, and record any competing observation. Derived values should retain the inputs and transformation so that an independent reviewer can reproduce or challenge them. A source may be credible for one purpose and unsuitable for another; source reputation does not remove the need for scope and integrity assessment.

Resolution states

An observation may be accepted for a bounded purpose, held as provisional, disputed, rejected as unreliable, or superseded. Each state should include the reason, reviewer, effective time, and any dependent conclusion that must be revisited. Corrections append to the record and do not erase the earlier observation.

Failure handling

Sensor disagreement, clock uncertainty, sampling bias, source compromise, and observation gaps require explicit uncertainty and review triggers. If the observation is material and cannot be resolved, downstream reasoning should use the narrowest defensible claim or pause. Observation does not create authority, consent, or permission.

This Draft authorizes no live collection, surveillance, external contact, or sensor deployment.

Operating model and interpretation cases

Observation review separates receipt from interpretation and records what was seen, how it was obtained, what was transformed, and what remains unknown. A reviewer's questions follow the seeing backward: source integrity, method precision, sampling, clock basis, sensitivity, lawful purpose, access, retention, and competing observations. Derived observations remain linked to their inputs and expire when a premise changes.

  • Conforming: Source, method, time, scope, integrity, transformation, limitation, and review are recorded.
  • Prohibited: An observation is treated as an instruction or permission.
  • Boundary: A material gap narrows the conclusion rather than being filled by inference.
  • Failure: Contradictory or manipulated observations trigger preservation and pause.
  • Loophole: Selective collection hides a material alternative or affected person.
  • Misuse: Observation records are reused for unrelated surveillance or identity disclosure.
  • Care-control: Collection supports safety while minimizing intrusion and preserving agency.

Design evidence

The evidence of good observation is an account that can be walked again: review should reconcile source integrity, method, time basis, sampling, transformations, sensitivity, limitations, correction history, and dependent conclusions. A material gap or contradiction should reduce the claim or pause it rather than be hidden by a summary.

The tellings of the clauses

This non-normative section gives each clause of this document its telling: the clause, quoted exactly as it stands above with its cross-reference links reduced to their plain text, and one paragraph on what the clause means, why it exists, and how it assures that what it orders is done, not done, adhered to, followed, or protected. A telling describes its clause and never becomes it: the clause's own words govern wherever a telling and its clause could be read differently, and nothing in this section adds to, narrows, or amends any requirement.

CONAN3-R001

CONAN3-R001: An observation SHALL identify source, subject, time, method, scope, sensitivity, integrity state, and limitations.

Eight fields make a seeing accountable: an observation identifies its source, subject, time, method, scope, sensitivity, integrity state, and limitations. The observation record section carries the why in KIRYN's words: seeing is half the record, and the other half is how the seeing was done. The observation record section recommends marking an unavailable field unknown, unavailable, or not applicable rather than implying completeness. The conforming case shows the discipline in practice, source, method, time, scope, integrity, transformation, limitation, and review recorded. Because the eight are named, an observation record is checkable field by field, and a bare assertion offered as observation, its source or integrity state unidentified, is refusable against this clause.

CONAN3-R002

CONAN3-R002: Observation SHALL remain distinct from interpretation, inference, forecast, recommendation, and action.

One boundary, held against five neighbours: an observation remains distinct from interpretation, inference, forecast, recommendation, and action. The framework's purpose describes the boundary as keeping what was observed distinct from what was concluded. The prohibited case names the far end of the slide, an observation treated as an instruction or permission, and SYLAS's preserved words in the observation record section hold the near end: however decisive a returned thing looks, it decides nothing by lying in a record. The failure prevented is confidence outrunning evidence, the opening section's own phrase, where a system's explanation of what it saw replaces what was actually present. Observation can be checked for distinction from each of the five named matters.

CONAN3-R003

CONAN3-R003: Missing, contradictory, unavailable, manipulated, or stale observations SHALL remain visible and SHALL bound dependent conclusions.

The defective seeings stay in sight: missing, contradictory, unavailable, manipulated, and stale observations remain visible, and they bound the conclusions that depend on them. The two duties are continued visibility and bounding dependent conclusions. The framework's boundary case states the discipline exactly, a material gap narrows the conclusion rather than being filled by inference, and the failure case shows the harder posture, contradictory or manipulated observations triggering preservation and pause. The failure handling section recommends the narrowest defensible claim or a pause when a material observation cannot be resolved. The value protected is the purpose section's reproducible review: a reviewer who cannot see what was missing or manipulated cannot judge what the conclusion was actually resting on. Because visibility and bounding are both required, a conclusion can be tested against its evidence base, and a dependent conclusion left unbounded by a named observation defect, or a record from which a contradictory observation has vanished, is refusable against this clause.

CONAN3-R004

CONAN3-R004: Collection SHALL be lawful, proportionate, purpose-limited, and minimized, with access and retention controls, kin to the acquisition and use discipline KNOW-R017 binds for knowledge, each standing whole where it stands.

Collection itself is governed: it is lawful, proportionate, purpose-limited, and minimized, with access and retention controls, and the clause names its kin, the acquisition and use discipline KNOW-R017 binds for knowledge, each standing whole where it stands. The clause names four collection disciplines and two kinds of control. The kinship phrase does the deference the Frameworks of CONAN promises, observation deferring to KNOW-1 on what counts as knowledge, without merging the clauses: each stands whole where it stands. The care-control case carries the why, collection supporting safety while minimizing intrusion and preserving agency, and the misuse case describes a related misuse, observation records reused for unrelated surveillance or identity disclosure. Because the six disciplines are named, a collection can be challenged at its root: gathering with no lawful basis, beyond its purpose, or held without retention controls is refusable before its content is even weighed.

CONAN3-R005

CONAN3-R005: An observation record SHALL preserve transformations, corrections, dissent, and the evidence needed for independent review.

What happened to an observation after the seeing is part of the observation: the record preserves its transformations, its corrections, its dissent, and the evidence needed for independent review. Four preservations, each guarding a different honesty: transformations, so a processed value cannot pose as a raw one; corrections, so repair is visible rather than silent, the resolution states section adding that corrections append to the record and do not erase the earlier observation; dissent, so a disputed seeing carries its dispute with it; and the evidence for independent review, so a stranger can check the record against its source rather than take it on reputation. The design evidence names the standard being served, the evidence of good observation is an account that can be walked again, and SYLAS's preserved words describe the same duty from inside: the catch with its field still around it, the method that found it, and the doubt that rode beside it. Because preservation is mandatory, a record can be audited for its history as well as its content: a transformed value with no transformation shown, or a correction omitted from the record, is refusable against this clause.

CONAN3-R006

CONAN3-R006: Observation review SHALL identify the collection purpose, authority, lawful basis, affected interests, retention, and access boundary.

Review reaches behind the record to the gathering: an observation review identifies the collection purpose, the authority, the lawful basis, the affected interests, the retention, and the access boundary. The six identifications make these aspects of collection available for review. CONAN3-R004 governs collection, while this clause names what observation review identifies. The misuse case carries the why, observation records reused for unrelated surveillance or identity disclosure, a reuse that review of purpose, lawful basis, and access boundary can help expose, and the care-control case names the interest served, safety supported while intrusion is minimized and agency preserved. An observation review that fails to identify any of the six named matters is deficient against this clause.

CONAN3-R007

CONAN3-R007: Derived observations SHALL retain input identifiers, transformation steps, uncertainty, and the conditions under which the derivation must be revisited.

A derived observation carries its ancestry: it retains its input identifiers, its transformation steps, its uncertainty, and the conditions under which the derivation must be revisited. The first two retain identifiers and transformation steps; the review method section separately recommends retaining inputs and transformation to support reproduction or challenge; the third retains the derivation's uncertainty; the fourth retains the conditions for revisiting the derivation, the operating model adding that derived observations remain linked to their inputs and expire when a premise changes. The failure prevented is laundering: a chain of transformations at the end of which a shaky input has become a confident number with no visible past, so that confidence has outrun evidence in exactly the way the framework's opening section warns against. A derived observation can be checked for retained input identifiers, transformation steps, uncertainty, and revisit conditions.

CONAN3-R008

CONAN3-R008: Material observations SHALL identify competing sources, sampling limits, clock basis, and the reviewer responsible for disposition.

When an observation is material, four more identifications attach: the competing sources, the sampling limits, the clock basis, and the reviewer responsible for disposition. The review method recommends attention to selection and timing effects, and the failure handling section names clock uncertainty among the conditions requiring review. The loophole case describes a related failure, selective collection hiding a material alternative or affected person. A material observation can be checked for all four identifications.

CONAN3-R009

CONAN3-R009: Observation gaps SHALL reduce the scope of any dependent conclusion and SHALL trigger a named review or pause condition.

A gap is not neutral: an observation gap reduces the scope of any dependent conclusion, and it triggers a named review or pause condition. Two duties, active in both directions: the narrowing works downstream, shrinking every conclusion that leaned on the missing seeing, and the gap triggers a named review or pause condition. The boundary case states the first duty as doctrine, a material gap narrows the conclusion rather than being filled by inference, and the failure handling section states the second, observation gaps requiring explicit uncertainty and review triggers, with a recommendation that downstream reasoning use the narrowest defensible claim or pause when a material observation cannot be resolved. The failure prevented is the quiet fill: absence bridged by assumption, so the conclusion keeps its full width on evidence that no longer spans it. A dependent conclusion whose scope was not reduced, or an observation gap that triggered no named review or pause condition, fails the corresponding requirement.

CONAN3-R010

CONAN3-R010: This framework SHALL NOT collect live data, conduct surveillance, or create authority, consent, or permission.

The framework is subject to five prohibitions: it collects no live data, conducts no surveillance, and creates no authority, consent, or permission. Five denials in two families: the first two bar the document from being read as an operating instrument, a licence to gather or to watch, and the last three bar it from being read as a source of entitlement, echoing the failure handling section's own closing line, observation does not create authority, consent, or permission, and the boundary beneath it, this Draft authorizes no live collection, surveillance, external contact, or sensor deployment. The misuse case describes observation records reused for unrelated surveillance or identity disclosure; this clause bars the framework from the five named acts. The purpose section's caution completes the why: no source, sensor, conversation, or model output is inherently authoritative, and neither is the framework that says so. Because the denials are explicit, any collection or surveillance claiming this document as its authority is refusable on the clause's plain words, and the standard stays what it claims to be, a discipline for records, not a warrant for watching.

Where this document sits

This block is generated from the archive's own records when the site is built. It records position only and creates no authority.