228 lines
9.1 KiB
Plaintext
Executable File
228 lines
9.1 KiB
Plaintext
Executable File
WHAT REMAINS — RC2 Revised Tarball
|
|
====================================
|
|
|
|
This file tracks content from the source sessions and the independent
|
|
review that has NOT been incorporated into the specification.
|
|
|
|
All review findings have been addressed in one of three ways:
|
|
FIXED — The issue has been resolved in the revised files
|
|
PARTIAL — Addressed but a residual gap remains
|
|
DEFERRED — Acknowledged as a known gap for a future phase
|
|
|
|
---
|
|
|
|
|
|
REVIEW FINDINGS STATUS
|
|
=======================
|
|
|
|
S-1 Dual Charter FIXED
|
|
Root CHARTER.md is now a navigation pointer.
|
|
spec/oe-0000-charter.md is the sole authoritative charter.
|
|
|
|
S-2 Triple-Distributed Editorial FIXED
|
|
reference/editorial-principles.md is now the sole
|
|
authoritative source. All other documents reference it.
|
|
|
|
S-3 Laws/ and spec/ relationship FIXED
|
|
All spec documents now include "Applicable Laws" section
|
|
referencing laws/engineering-laws.md.
|
|
|
|
S-4 Bootstrap Problem (OE-0011) PARTIAL
|
|
OE-0011 now explicitly acknowledges the constitutional
|
|
governance gap. The gap itself is not resolved — a
|
|
future amendment is required.
|
|
|
|
T-1 Observation Definition/Usage FIXED
|
|
OE-0004 now distinguishes Direct Observation from
|
|
Corroborated Observation. The translation examples are
|
|
presented under corroborated observation with engineering
|
|
confirmation evidence.
|
|
|
|
T-2 Knowledge vs Understanding FIXED
|
|
OE-0006 no longer redefines knowledge. Understanding is
|
|
defined on its own terms.
|
|
|
|
T-3 Bedrock Term Collision DEFERRED
|
|
Acknowledged. "Bedrock" has a geotechnical meaning.
|
|
No rename applied — the term is deeply embedded in the
|
|
project's identity. Enduring Concept test (Law 5) would
|
|
flag this if evaluated strictly. The project may choose
|
|
to rename or to accept the collision.
|
|
|
|
T-4 The Thread — Untestable Model FIXED
|
|
OE-0001 now defines four testable properties of the
|
|
thread: deliberate maintenance, carries understanding,
|
|
measurable integrity, breaks when context is lost.
|
|
OE-0010 defines thread integrity as testable by whether
|
|
a practitioner can reconstruct reasoning.
|
|
|
|
T-5 Evolution Term Usage PARTIAL
|
|
Renamed to "disciplined, verified extension" in the
|
|
definition. The document title remains "Evolution" —
|
|
same collision issue as T-3.
|
|
|
|
SP-1 No Operational Context Def FIXED
|
|
OE-0003 now defines a minimum context record structure
|
|
with 8 required fields and 3 supplementary fields,
|
|
plus a completeness criterion.
|
|
|
|
SP-2 Understanding-Verification Circ FIXED
|
|
OE-0006 no longer uses "verified" in the definition of
|
|
understanding. Understanding is "a contextualized model
|
|
of reality derived from observation and survey."
|
|
Verification (OE-0007) is the process applied to it.
|
|
The dependency chain is now acyclic.
|
|
|
|
SP-3 No Conformance Clause PARTIAL
|
|
OE-0000 now defines conformance basis at a high level:
|
|
"contains the minimum required fields, follows editorial
|
|
principles, respects dependency integrity." Detailed
|
|
conformance testing criteria deferred to Implementation
|
|
Phase.
|
|
|
|
SP-4 Stub Documents FIXED
|
|
OE-0005 (Survey) now has a concrete 5-field structure.
|
|
OE-0007 (Verification) now defines the verification loop
|
|
explicitly. No forward references to undefined content.
|
|
|
|
E-1 Meta-Commentary FIXED
|
|
All authorial asides removed from spec documents.
|
|
|
|
E-2 Rhetorical Formatting FIXED
|
|
Negation lists and emphatic repetition removed from
|
|
spec documents.
|
|
|
|
E-3 Inconsistent Status Labels FIXED
|
|
OE-0000 now defines the status lifecycle:
|
|
Draft -> Proposed -> RC -> Accepted -> Deprecated.
|
|
All documents set to Draft for consistency.
|
|
|
|
I-1 No Implementable Artifact FIXED
|
|
OE-0003 now defines a concrete context record structure.
|
|
The bridge example demonstrates a populated record.
|
|
This moves the standard from fully abstract to
|
|
partially implementable.
|
|
|
|
I-2 Empty Directories DEFERRED
|
|
website/, implementations/, schemas/, tools/ remain
|
|
empty. They are structural placeholders. Their content
|
|
will be defined during the Implementation Phase.
|
|
|
|
EG-1 Translation Evidence DEFERRED
|
|
The claim that translation produces better outcomes
|
|
is still asserted without empirical evidence. This is
|
|
an evidence gap that requires real-world testing.
|
|
|
|
EG-2 Context Preservation Evidence DEFERRED
|
|
The claim that context preservation reduces re-derivation
|
|
cost is asserted but not quantified. Requires empirical
|
|
study.
|
|
|
|
EG-3 Historical Citations PARTIAL
|
|
The Antikythera example now states "comparable complexity
|
|
in geared mechanisms" (more precise than "nothing of
|
|
comparable complexity"). Full citations still deferred.
|
|
|
|
EG-4 "Engineers Already Speak This" FIXED
|
|
OE-0002 now states "Engineers across disciplines share a
|
|
conceptual vocabulary" without the empirical claim.
|
|
|
|
R-1 Stewardship/Inheritance FIXED
|
|
Sharply distinguished: Stewardship = transmit discipline,
|
|
Inheritance = receive discipline. Different failure modes
|
|
(neglect vs passivity).
|
|
|
|
R-2 Thread/Inheritance FIXED
|
|
Sharply distinguished: Thread = the channel model,
|
|
Inheritance = the act of engaging with what the
|
|
channel carries. OE-0010 makes this explicit.
|
|
|
|
R-3 Translation in Four Places FIXED
|
|
Translation is defined in OE-0002, with authoritative
|
|
rules in reference/editorial-principles.md. All other
|
|
documents reference, not reproduce.
|
|
|
|
P-1 Bedrock as Epistemology PARTIAL
|
|
OE-0001 now defines bedrock as "reality — the physical
|
|
world, the constraints of materials and physics, the
|
|
behavior of systems under load" — more concrete than
|
|
the previous "immutable reality." Acknowledges that
|
|
understanding is always provisional. Does not address
|
|
the philosophical realism objection explicitly.
|
|
|
|
P-2 Thread Untestable FIXED
|
|
See T-4 above.
|
|
|
|
M-1 No Engineer/Engineering Def FIXED
|
|
OE-0000 now defines domain of applicability with
|
|
specific engineering disciplines listed.
|
|
|
|
M-2 Tacit Knowledge FIXED
|
|
OE-0003 now explicitly acknowledges the limitation:
|
|
"The standard acknowledges this limitation and aims to
|
|
preserve the explicit portion as completely as possible."
|
|
|
|
M-3 Confidentiality/Security FIXED
|
|
OE-0003 now acknowledges: "The standard defines the
|
|
structure of context records but does not define access
|
|
control mechanisms. Implementations must address
|
|
confidentiality, security, and access control as required
|
|
by their domain."
|
|
|
|
M-4 Incorrect/Obsolete Context FIXED
|
|
OE-0009 (Stewardship) now includes: "Stewardship includes
|
|
the obligation to identify and flag context that has
|
|
become obsolete or that was incorrect when inherited."
|
|
|
|
M-5 No Versioning Scheme FIXED
|
|
OE-0000 now defines versioning: independent document
|
|
versioning with MAJOR.MINOR.PATCH-status pattern.
|
|
|
|
|
|
RC2 SESSION CONCEPTS STATUS
|
|
===========================
|
|
|
|
Law of Enduring Concepts FIXED (Law 5 in engineering-laws.md)
|
|
Five-Question RC2 Gate FIXED (editorial-principles.md Section 4)
|
|
Self-Fading Example FIXED (editorial-principles.md Section 6)
|
|
Specification-first Architecture PARTIAL (concept acknowledged in
|
|
OE-0011, ROADMAP; not yet a formal
|
|
directory-level concept)
|
|
Compression Principle FIXED (Law 6 in engineering-laws.md)
|
|
RC2 Exit Criteria FIXED (ROADMAP.md)
|
|
RC2 Acceptance Criteria FIXED (ROADMAP.md)
|
|
RC2 Milestone Statement DEFERRED (not incorporated into spec
|
|
documents — it's process metadata,
|
|
not specification content)
|
|
|
|
|
|
REMAINING GAPS (Not Addressed in This Revision)
|
|
================================================
|
|
|
|
1. Constitutional governance layer (S-4 PARTIAL)
|
|
OE-0011 acknowledges the gap. No solution implemented.
|
|
|
|
2. "Bedrock" and "Evolution" term collisions (T-3, T-5 DEFERRED)
|
|
Both terms have established meanings in engineering that
|
|
differ from Open Engineer's usage. The Enduring Concept test
|
|
(Law 5) would flag both if applied rigorously to the
|
|
standard's own terms.
|
|
|
|
3. Detailed conformance testing criteria (SP-3 PARTIAL)
|
|
The high-level conformance basis exists. Testable criteria
|
|
for "does a context record comply?" do not.
|
|
|
|
4. Empirical evidence for core claims (EG-1, EG-2 DEFERRED)
|
|
Translation producing better outcomes and context preservation
|
|
reducing cost are asserted but not quantified.
|
|
|
|
5. Full historical citations (EG-3 PARTIAL)
|
|
|
|
6. Philosophical realism objection (P-1 PARTIAL)
|
|
The bedrock definition is more concrete but the
|
|
epistemological assumption remains unaddressed.
|
|
|
|
7. A contemporary, multi-discipline worked example
|
|
All four examples are from historical contexts. A
|
|
software engineering or biomedical context record example
|
|
would strengthen cross-discipline applicability claims. |