Assistant: codex Assistant-Model: gpt-6-astra Assistant-Session: 01a0e241-8285-7a63-8c0c-51c9cb824dc3
38 lines
3 KiB
Markdown
38 lines
3 KiB
Markdown
# Ontology review for the 0.1 reference subset
|
|
|
|
2026-09-27, Codex author-model editorial review. Owner WP-0003 T03.
|
|
**Bounded result: retain with qualifications. M2 remains open.** No general proof
|
|
of minimal responsibilities, independent dimensions or complete pattern recurrence.
|
|
|
|
## Conflict Copy versus Explicit Reconciliation
|
|
|
|
Retain two research identities for preview retrieval:
|
|
|
|
- Conflict Copy answers “how do we keep detected competing content available while
|
|
continuing work?” Its result is preserved divergence, not resolved meaning.
|
|
- Explicit Reconciliation answers “how do we decide intended content and record the
|
|
decision?” It can use a version store without making a separate conflict file.
|
|
|
|
Preservation may precede manual review, but may also be followed by a justified
|
|
automatic merge or a deferred decision. Manual comparison can receive alternatives
|
|
from a revision store. Therefore neither unconditional requires edge is justified.
|
|
Export one conditional creates-context-for edge from CAND-0001 to CAND-0004 and
|
|
state the conditions. This is conceptual reasoning, not an observed independent
|
|
implementation of both complete contracts. Test whether readers can select one
|
|
without being forced into the other; merge later if that distinction proves unhelpful.
|
|
|
|
## Other decisions
|
|
|
|
| Question | Preview disposition | Limit |
|
|
| --- | --- | --- |
|
|
| Pending Synchronization versus Mutation Outcome Tracking | Retain both: local work may already be accepted while remote propagation is pending; remote write acceptance may instead be unknown | Shared operation-state model may motivate later refactoring; no full recurrence claim |
|
|
| Version precondition versus operation identity | Distinct obligations: stale-base rejection versus recovery of a particular attempt | One does not establish the other; receiver semantics must be checked |
|
|
| Local draft versus locally accepted record | Retain separate; editable intent need not be durable or locally authoritative | Add persistence only under explicit policy/storage requirements |
|
|
| Authority, projection and delivery | Apply the [six-question aid](AuthorityProjectionComparison.md); retain the six seeds without new drafts | Separate decisions with compatibility constraints, not universally independent axes |
|
|
| Families versus responsibilities | Keep separate classification fields; quality is a family, reconciliation a responsibility | Provisional direct-mechanism assignments and selected forces are not exhaustive ontology proof |
|
|
| Relations and prerequisites | Export only scoped proposals with rationale; no inverse, symmetric or transitive inference | Proposed links are not canonical graph edges; contextual conditions are not pattern IDs |
|
|
| Scale coverage | Preserve current labels and gaps, including L0/L7 | No automatic relabeling to fill empty cells |
|
|
|
|
No M2-CoverageReview pass is claimed: VC-04/05 are absent and VC-03/06 remain provisional.
|
|
This closes the preview's bounded ontology inspection, not WP-0003 T03. Independent
|
|
retrieval/usefulness and broader case outcomes may overturn these provisional choices.
|