Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2073

A worker records an observation in one command

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
a-session-leaves-what-it-observed
Milestone status
DONE
Wave
0
Waiting on
none
Holds back
I2074
Behind it in all
2
Evidence
1 of 1

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2073

majordomus plan verify I2073

majordomus plan done I2073

What it is

Objective
Register observation.recorded in share/events.yaml (emitted_by knowledge; requires task_id, kind, subject, statement, evidence) and add `knowledge observe --kind <friction|workaround|defect|drift|repetition> --subject <ref> [--evidence <ref>]... <statement>` to lib/knowledge.sh, writing one ledger line, refusing malformed input without writing, inside or outside a task, and only inside an open episode; write ADR 0118.
Why
Friction is noticed by workers and written nowhere the repository reads; decision add is the precedent for one typed line per act.
Now
No observation event or command exists; workers keep friction in private memory files.
Wanted
One command any provider can run inside an episode; one typed ledger line per observation.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • An observation inside an episode writes one line with kind, subject, statement, each evidence reference and the active task or none
  • An unknown kind, a malformed subject or evidence reference, a multi-line statement or a transcript marker is refused with exit 2 and no line
  • A subject is a repository path or capability:, rule:, command:, gate: followed by an identifier, and anything else is refused
  • With no open episode the observation is refused with exit 10 naming session start, and nothing is written
Validation
bash test/run.sh 980_a_session_records_what_it_observedbash test/run.sh 33_event_registry
Evidence required
observation_recorded
Evidence present
observation_recorded

Scope

Touches
lib/knowledge.shshare/events.yamlshare/commands.yamldocs/CLI.mddocs/KNOWLEDGE.mddocs/SCHEMAS.mddocs/CLAIMS.yamldocs/claimsdocs/CONCEPTS.md.ai/repo/adrstest/cases/980_a_session_records_what_it_observed.sh
Not
unknown: the record declares no `non_scope`
Depends on
none
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-09
Updated
2026-10-14T08:01:33Z
Started
2026-10-14T08:01:27Z
Verified
unknown: the record declares no `verified_at`
Completed
2026-10-14T08:01:33Z

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.