Skip to content

Match the coverage map review wording #187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
CuriousOne23 merged 1 commit into from
Oct 8, 2026
Merged

Match the coverage map review wording #187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 6 additions & 4 deletions ...s_20/system_playground/simulation/pathA_short_sim/notes/program/coverage_map.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,9 @@ Door: [../../README.md](../../README.md). Status: [status.md](status.md).

Path A will be criticized because this work has no settled outside result. The answer is not that the theory is finished. The answer is a map. A critic can point at a hole. The hole is already named.

Human conversation space is the territory. Path A coverage space is the owner and the evidence. Roadmap completeness means the recognized forms are named, assigned a status, and open to revision. It does not mean human conversation space is exhaustively known. The rows are a proposed, extensible inventory, not a closed ontology.
Human conversation space is the territory. Path A coverage space is the owner and the evidence. Roadmap completeness means every currently recognized conversational form has a named row and an explicit status. It does not mean human conversation space is exhaustively known.

The rows form a proposed and extensible inventory. They are informed by established conversational classifications, but they are not a closed or universally accepted ontology. A newly recognized conversational form is added as a named row rather than silently absorbed into an existing row.

## Status words

Expand All @@ -20,13 +22,13 @@ Human conversation space is the territory. Path A coverage space is the owner an
| `unsupported` | Tested, and the packet could not account for it without invention. |
| `unknown` | No realization yet. Historical rows stay here until a later owner is exercised. |

A check without a replay is not `covered`. Every covered row names the executable evidence that earns that status.
A check without a replay is not `covered`. Every covered row must identify the replay or ledger row that demonstrates its coverage.

## Present-only

These forms use the current utterance only. History is not an input.

| Form | Pipeline | Status | Evidence |
| Form | Realization path | Status | Evidence |
|---|---|---|---|
| Assertion / state | SOB, SROB, CnOB, SmOB, IdOB | covered | `claim_ledger_replay.py`: *The sky is blue.* |
| Location | SOB, SROB, CnOB, SmOB, IdOB | covered | `claim_ledger_replay.py`: *The book is on the table.* |
Expand Down Expand Up @@ -60,4 +62,4 @@ History is on the map and out of the present sim. Owners are COB, CST, CIL, and

An extension is a new row, or a status change after a replay. `absent` becomes `covered` only when a replay exists. One absent form is the next development, chosen explicitly. This page does not add that sentence.

Pipeline means the form passes through those writers. The decisive writer for each form is unassigned. A later pass may name it. Partial support is not a status. A narrower form, such as simple predicate negation, gets its own row.
Realization path means the form passes through those writers. It is not a claim that each writer owns the distinctive capability. The decisive writer is unassigned. A later pass may name it. Partial support is not a status. A narrower form, such as simple predicate negation, gets its own row.
Loading