Isotope wiring: validation and export limits
Return to the editor · Separate 3D workbench
The hosted editor embeds the standalone examples/isotope-wiring/index.html. Its counts, validation, delta compiler and File operations belong to that legacy implementation. The new independent machinery described below is not connected to the visualization. A valid definition or matching inventory is not an established nuclear geometry, isotope stability result, or complete equivalence certificate.
Known legacy limitations
| Case | Observed limitation | Practical consequence |
|---|---|---|
| Replay an identity delta | compile(diff(A,A), {A}) is rejected as cyclic because definition IDs and revision identity are conflated. | Do not assume identity/no-change deltas are a verified replay path. |
| Full-definition roundtrip | The existing graph projection can roundtrip while base-only metadata survives even when absent from the target definition. | A successful graph comparison does not certify metadata deletion or recovery of the whole original definition. |
| Generated cell IDs | Concatenated coordinates can give the same ID for (1,10) and (11,0) in a size-12 shell. | Distinct legal coordinates need distinct explicit identities; the independent adapter does not repair the editor's generator or ambiguous saved files. |
| Change a delta base | A mutable base can change the compiled target without changing the delta. | Keep the actual base and its provenance, not just a definition name or delta text. |
Retain original project exports and absolute definitions outside the app before editing or moving between browser locations. Inspect metadata as well as graph records when comparing exports. This is a caution, not a certified persistence or roundtrip guarantee. Do not rely solely on delta exports, displayed counts or an apparently unchanged drawing as a backup check.
The local legacy characterization suite distinguishes seven passing software checks from three expected unresolved requirements. TODO failures are not passes: the identity-delta, metadata-deletion and generated-ID assertions still fail under their TODO labels. A zero process exit with TODOs does not close those defects.
Separate machinery: implemented scope, not UI integration
The inspected pending local development includes several headless layers. These source paths are provenance locators, not promises of a stable public API; uncommitted files may be absent from a clean checkout of the published revision.
| Layer | Implemented local scope | Limits that remain |
|---|---|---|
core/finite-diagrams.mjs | Checked finite-incidence diagrams and structural maps; pointwise finite limits/colimits and open-component gluing with explicit witnesses. | Fixed schema presentation; bounded software tests are not a formal proof of implementation correctness. Closure of extra model constraints does not follow from ambient closure. |
core/legacy-adapter.mjs and attributed adapter | Absolute-definition import, explicit support interfaces, model labels and exact recovery of retained source data. | Recovery uses the retained original source, not an inverse of bare incidence. A modified/glued object is not automatically exported back into a current legacy definition. |
core/model-predicates.mjs | Versioned model predicates and checked support-policy composition, with localized verified/refuted/unknown/notApplicable statuses. | Z/N and shell targets are supplied targets, not derived observables. Model-valid objects are not composition-closed under the tested gluing; typed counterexamples are retained, not deleted to fit counts. |
core/revisions.mjs | In-memory immutable revisions, explicit ground rewrites, before-image undo, branch-head checks and dependency-complete bundle replay. | Undo restores a state while retaining a new history event. Browser autosave and legacy delta compilation are unchanged. Generic rewrite matching, cross-engine migration and selective evidence transport are not supplied. |
The draft examples/isotope-wiring/MACHINERY.md and companion core/CLOSURE.md, core/ADAPTER.md, core/MODEL.md and core/REVISIONS.md specify these local boundaries. They must not be read as a claim that the embedded editor already implements them. Imported unknown fields may be retained without being interpreted as structural incidence.
A model predicate can pass while a source fixture still records an unresolved placement. Likewise, a typed gluing can fail model predicates even when its inventory matches the supplied targets. Neither passing software coherence checks nor choosing an isotope name derives measured nuclear content or physical adequacy.
Reproduction and provenance
In a development checkout containing the pending suites, use:
node --test tests/isotope-wiring-core.test.mjs
node --test tests/isotope-wiring-category.test.mjs tests/isotope-wiring-adapter.test.mjs tests/isotope-wiring-model.test.mjs tests/isotope-wiring-revisions.test.mjsThe first command characterizes the actual legacy source and preserves its expected TODO failures. The second checks the independent software layers, not their integration into the app or physical isotope claims. Test totals are snapshot-specific; inspect TODO, failure and scope fields rather than treating a process exit as a universal certificate.
The standalone editor source and embedding component identify the running implementation. Pending development documents are not linked as though already available in that published revision. No formal theorem, legacy defect repair or physical admission is made by this limitations page.