Status and open points
This chapter is a draft for review, dated 2026-09-24.
This is that status chapter. It records what is decided, what the final review corrected, how Andy answered the six questions that were his, what is not built and the order the work starts in. The other eleven chapters state the model: constitution, records, source rows and patches, operations, values and time, evaluation, policy, conformance, extensions, packaging and proof cases.
What this draft is
The specification is an integration document. It names four records, gives every contract already in the tree a role in one of them and adds only what is missing. A chapter must name an existing contract rather than fork it (R4). A chapter that describes something not yet built must state that in the same sentence (plans/276-lolly-document-model.md status line, plans/276-execution.md section 3).
No shared type is frozen before the counterexample fixtures pass (plan section 18). Nothing is added to packages/core or schemas/ in this wave, and every proposed record appears as an indented draft shape instead (plans/276-execution.md section 3). A draft shape must never be read as a type, and no reader may treat a field name in one as stable.
This draft makes no conformance claim and states no threshold (C8), and it sets no latency target because the current evidence justifies none (plan section 18, review gate 5). It adds no reproducibility promise beyond the ones docs/determinism.md already makes. The probe numbers appear in one chapter, conformance, as evidence that a single whole-image number cannot separate a lost caption from a half-pixel shift (C8).
The notice at the head of every chapter must stay until this chapter records the required chapter review (plans/276-execution.md section 5). On 2026-10-15 a focused DAM review compared the draft with plan 312 and existing source, and Andy authorised the amendments and first wave in plan 314. That review covers the resource, evidence and authority boundary. Andy's answers of 2026-10-16 settle the six questions below. Neither completes the wider chapter review or freezes a shared type, so the notice stays. The constitution, source rows and patches, policy and conformance chapters most need that review, because later contracts depend on their semantics.
DAM amendment, 2026-10-15
The amendment keeps the four records and the confirmed pilots. It adds requirements for selected-file/representation identity, byte observations, imported evidence, scoped review and current source/processing authority. Rights reuse packages/core/src/rights-v1.ts; processing jobs and private evidence remain host or Lolly Work records. Records maps them, and proof cases adds cases 30 to 38.
These are draft requirements, not implemented shared contracts. Lolly Work's federated metadata version is a cache change token, not proof of immutable bytes. Its catalog admission and version curation are distinct from its implemented final-byte staged delivery approval. Adaptive publication and remote processing of finished variants require explicit new operation/delivery contracts before implementation. The policy, conformance and packaging chapters state those limits.
Wave 1 amends prose and runs focused executable evidence against existing seams. It changes no shared type, schema, wire order, engine version, package part, provenance write or live permission policy. Full DAM fixtures, a general historical provider resolver, contextual territory/channel evaluation and private portable evidence enforcement remain required work.
The index identifies this amendment as draft-2026-10-15; chapter notices retain the original draft date. Existing executable evidence covers only the following parts of the new cases:
| Evidence | What it establishes | What remains unproved |
|---|---|---|
shells/web/src/lib/asset-files.test.ts and lolly-work/tests/provider-source-observation.test.ts | Same-format file identities survive selection/reordering; previews stay separate; fresh byte observations distinguish an overwrite under unchanged metadata. | Durable exact provider pin retrieval and the full saved source-to-delivery case (30, 31). |
tests/rights-evaluate.test.ts | Existing rights decisions follow fingerprinted facts and do not automatically apply to a changed source or context. | General territory/channel eligibility and current upstream permission enforcement (32, 33). |
lolly-work/tests/delivery-api.test.ts, lolly-work/tests/catalog-versions.test.ts and lolly-work/tests/catalog-availability.test.ts | Existing staged approval/idempotent retry, version-curation boundaries and imported availability gates. | New source-proof review, remote processing reconciliation and adaptive publication (33, 36, 37). |
Passing those focused tests is not admission of a conformance fixture. Cases 34, 35 and 38 still require their full privacy, imported-recipe and package round trips.
Papirfly, Air and Adobe follow-up
The same wave now includes plan 315's production findings: historical bytes versus current attributes, typed content and locale bindings, explicit bounded action targets, destination write intent, asynchronous readiness, search-mode compatibility and review purpose/origin. Cases 39 to 44 state the required counterexamples. A campaign remains a host/Lolly Work record referencing the four document records; no fifth root or separate renderer is introduced (R1, R3, R4, R5, R8, R11, R15).
Focused evidence additionally exercises Lolly Work's current exposure predicate after an upstream approval change with unchanged bytes/cache token, and Lolly Batch's stable row mapping when a caller selects only failed rows. The first does not prove live upstream revocation or historical metadata retrieval. The second does not implement campaign persistence, content refresh, proof-set review or remote commit checks. Cases 39 to 44 remain unimplemented end-to-end requirements.
Plan 314's later order is paged library, source/history, controlled campaign production, governed discovery and selected processing/delivery. Plan 191 owns portable locale/matrix descriptions; Lolly Work plan 43 owns persisted campaigns. Vendor qualification may proceed independently, and no new adapter is enabled by this draft.
Confirmed decisions
These come from Andy's recorded direction. They are settled and must not be reopened by a chapter (D1 to D13).
| ID | Decision | Chapter that carries it |
|---|---|---|
| D1 | The document represents a complete tool: its interface, behaviour, dependencies, permitted changes and operations. | constitution |
| D2 | The pilots are Lolly Design, Chart and Agenda: Lolly Design spans print, raster and motion, Chart tests nesting and typed data, Agenda spans interactive web, slides and motion. | proof cases |
| D3 | A claimed renderer suite must pass reference-render fixtures, because a valid JSON tree is not evidence of a render. | conformance |
| D4 | Typed declarative behaviour is preferred, with an imperative escape hatch that carries its own execution and trust contract. | values and time |
| D5 | Spatial and fabricated outputs are extensibility examples, never priorities or gates for 0.1. | extensions |
| D6 | Constraints may travel with a tool and may also be supplied by Lolly Work, and the two are modelled separately. | policy |
| D7 | Outside a governed instance the local person may accept or reject a constraint, and the rejection has an explicit representation. | policy |
| D8 | Still-image fidelity allows a very low pixel difference, difficult to notice without close inspection. | conformance |
| D9 | Motion must match time and look similar at corresponding percentage points, with extra coverage around transitions. | conformance |
| D10 | Independent authors may publish feature namespaces and conformance fixtures. | extensions |
| D11 | Some operations are non-recordable or non-replayable, and a utility may act on files without rendering anything. | operations |
| D12 | Reference and acceptance authority is the Lolly Work administrator for a governed brand and the local person otherwise. | policy |
| D13 | The model reads well to the Kubernetes, Penpot and Rive communities in their own idioms, as direction and not as instruction. | records |
D8 is restated by the comparator probe, not reopened. Andy's intent is no visible loss under close inspection, and the conformance chapter tests that intent with three declared checks instead of one number (D8, R9).
Resolutions adopted from evidence
Each resolution is adopted unless Andy objects (R1 to R15). A chapter must cite the resolution id, or a repository path, beside the rule it states (plans/276-execution.md section 3).
| ID | Resolution | Chapter |
|---|---|---|
| R1 | The canonical source is flat rows keyed by permanent id, one owner pointer and one order key, with structured values in typed payload records and patches carrying a base revision. | source rows and patches |
| R2 | Declarative logic is a closed JSON expression tree with a static cost estimate refused at authoring time and a runtime budget per evaluation, and showIf stays as its v0 subset. | values and time |
| R3 | Imperative logic stays in hooks, specified as eight protocol contracts with an authored effect envelope, per-attempt grants and an execution class that enforces them. | values and time |
| R4 | The four records map onto existing persisted forms, and the compile result is transient and never persisted as a document. | records |
| R5 | One outcome vocabulary with three separate parts: a typed result, a record of committed artifacts and a termination, with review states on a run lifecycle beside it. | operations |
| R6 | Effective policy resolves authority first, then composes attributed layers, and a local waiver deactivates a named waivable creative rule only in unmanaged execution. | policy |
| R7 | A governed client that loses its connection keeps enforcing the policy it holds, and refresh due, update known, policy validity and attestation stay four separate facts. | policy |
| R8 | Measured conformance is a suite report with core and extended features, and contextual acceptance is a separate record naming the authority and each exception. | conformance |
| R9 | The still-image comparator is three checks declared per fixture: a whole-image fuzz band, region-scoped measures and semantic checks on the artifact. | conformance |
| R10 | Extensions live in a namespaced map with used and required lists, a version per extension and a complete dependency scope a host without it must protect. | extensions |
| R11 | Every record carries its own version, readers upgrade on read, a container carries a minimum reader and one internal evaluator normalises the four gates. | packaging |
| R12 | Native 0.1 is one still-image suite, still-2d/1, over PNG, SVG and PDF, with motion staged after the timeline contract and interactive output kept as an adapter. | conformance |
| R13 | Unpack, Prepare, Batch, Verify and the Rebrand review get operation adapters with typed inputs and outcomes, and none of them needs a canvas. | operations |
| R14 | A chart inside Lolly Design is a layer kind whose row references a chart payload record by id, lowered by pure engine code and replaced as one atomic value. | source rows and patches |
| R15 | An evaluation receipt records the definition and instance revisions, the resolved fonts by digest, the shaping engine, the emoji set, the clocks, the effective policy version and the execution class. | evaluation |
Corrections from the final review
Codex reviewed the finalised plan on 2026-09-24. Every finding was checked against the code before it changed the plan, and all of them held. A chapter must not restate a claim these corrections removed (C1 to C9); the Change column of plan section 0.1 records what each one removed.
| ID | Correction | Verified against |
|---|---|---|
| C1 | Typed values cannot travel in the scalar collaboration rows, so typed payload storage is specified apart from flat ownership. | packages/core/src/canvas-op-v1.ts, schemas/canvas-op.schema.json |
| C2 | Two valid reparents merge into an ownership cycle in either delivery order, and a revision precondition alone cannot prevent it. | plans/276-document-model-evidence/crdt-cycle-probe.mjs over packages/core/src/canvas-op-v1.ts, and services/mcp/src/tools.ts for the stateless edit path |
| C3 | The single-file rule does not generalise, because an inspection succeeds with no artifact and a cancelled batch keeps the files it wrote. | packages/core/src/file-operation-v1.ts, packages/node-shell/src/rebrand-run-manifest.ts |
| C4 | Placing a local decision below the authored required rules makes a local rejection ineffective, so authority resolves first. | Read of the authority rule in plan section 10.1 |
| C5 | Offline answers unreachable rather than stale, cached material keeps working, Leave removes rather than forks and "Make an editable copy" is a separate action. | shells/web/src/lib/design-system/hosted.ts, shells/web/src/lib/instance-leave.ts |
| C6 | A generated effect inventory is a regular-expression scan that an alias evades, so it is lint and never authority. | scripts/tool-requires.ts, engine/src/runtime.ts |
| C7 | Preserving unknown fields at parse time is not a round trip, because the writer rebuilds its manifest from typed input on every save. | shells/web/src/lib/lolly-pack.ts |
| C8 | The probe supports the direction and settles no method, and an incomplete comparison must never pass. | engine/src/compare.ts |
| C9 | The tool count is two numbers, not one: 81 raw directories with 79 distinct ids, and the tools a content profile resolves, which is 67 for lolly-start and 77 for suse. The evidence scripts were also made rerunnable from the repository, and the retained comparator fixture was regenerated from the measured transformation. | packages/node-shell/src/content-roots.ts |
Five compatibility gates came from the same review and are stated in the chapters they affect. The public requires field keeps its meaning. Diff gains a source-aware path. An unmet extension is refused at the operation boundary. Aggregate work is bounded, and not only expression size. Incremental edits are measured on a device before any responsiveness claim.
Answered questions
Six questions were Andy's. Each had a recommended default so that drafting could proceed without an answer (plan section 16). On 2026-10-16 Andy accepted the defaults for Q1 to Q5 as this table states them, and recorded Q6 as decided: the specification is public from its first draft. A chapter that depends on one of these questions states the decision in its Open points (plans/276-execution.md section 1A). The last column keeps the evidence that would reopen a question.
| ID | Question | Decision, 2026-10-16 | Evidence that would reopen it |
|---|---|---|---|
| Q1 | The first editable interchange routes per pilot. | Default accepted. The four routes and three edits in the conformance chapter. | A customer route that outranks them. |
| Q2 | The granularity and persistence of a local rejection. | Default accepted. Per rule, instance-scoped, recorded on the session record against a fingerprint of the facts. A derived tool revision is a Design tool export and is not part of 0.1 (R6). | A need to share a rejected state as a reusable tool. |
| Q3 | What freshness a governed-claim export needs, and who states it. | Default accepted. Freshness is a policy rule the instance issues, with a validity interval and a stated behaviour when it cannot be established. With no such rule the held policy is enforced, and the receipt says which policy version was evaluated and when it was last attested. Leave and "Make an editable copy" keep their current meanings (R7). | An organisation that needs a hard deadline, or a fully offline site. |
| Q4 | What non-recordable means for a local utility and for a live-input tool. | Default accepted. Utility: capture off, retention none, replay semantic from pinned inputs. Live input: capture unsupported unless the person turns it on, retention session, replay none. | A regulated workflow that needs durable receipts for utilities. |
| Q5 | Who may publish a suite under the lolly namespace, and how a local or Lolly Work suite is named. | Default accepted. Suites under lolly/ are published from this repository's continuous integration only, instances publish under work:<instance>/, people publish under local/* and an acceptance record always states the suite it judged (R8). | A partner programme that needs a shared namespace. |
| Q6 | Whether the specification is public from the first draft. | Public, decided. The specification is published from its first draft, because docs/constraints.md, docs/determinism.md and docs/reproducibility.md already make public promises this model keeps. | A reason to keep the drafts private until the pilots pass. |
What is not built
The full document model is not implemented. Two parts have implementation evidence: the vm class runs rondocode songs (plan 301, packages/rondo/src/vm.ts), and plan 295 compiles Lolly Design rows into engine-internal drawing operations consumed by preview and admitted SVG, SVGZ and PDF exports. Values, expressions, code and time states the vm contract; evaluation and conformance record the export evidence and its limits. Neither part freezes the draft shared types or establishes a released conformance suite. The list below is what a reader must not assume exists.
- No shared document type and no schema.
packages/core/src/document-v1.tsandschemas/document-v1.schema.jsondo not exist. - No shared outcome, receipt, report or acceptance type.
packages/core/srcholds noOutcomeV1,EvaluationReceiptV1,ConformanceReportV1orAcceptanceV1(R5, R8, R15). - No expression, rule, timeline, dependency graph or accessibility finding type, and no
ComponentDefinitionV1. Plans 190, 191, 192, 194, 195 and 196 define them and none is built. Plan 193 is partly built, and itsChartSpecV1is inpackages/core/src/chart-v1.ts(plan section 0, F2). The component v0 does exist:packages/core/src/design-tool-v1.tsholdsDesignToolDraftV1, and plan 190's type is specified as its generalisation (plan section 6.4). - No conformance suite and no fixtures.
tests/conformance/does not exist, and no suite version has been released (R8, R12). - No three-check comparator.
engine/src/compare.tsre-exportscompareStructureandcomparisonBudget, and its visual mode answers a preview-grade whole-image comparison. No band is calibrated (R9, C8). - No chart layer kind. Composition still produces a flattened image, which the proof cases record as a failing case rather than the pilot (R14).
- No operation adapters for Unpack, Prepare, Batch, Verify and the Rebrand review (R13).
- No patch envelope and no source-aware diff.
engine/src/document-api.tsstill diffs hydrated HTML (R1). - No device measurements. No latency target is justified by the current evidence, and none is stated (plan section 18).
The order the work starts in
The work starts in this order, each step small.
- The vocabulary and the record map as public prose, with authority, authored identity, typed payload storage, operation results and committed-effect semantics worked as concrete examples (R4). In progress: this specification and the summary page
docs/document-model.mdare that step, pending the read described above. - The counterexamples of the proof cases chapter as contract fixtures, covering the scalar row boundary, the concurrent cycle, partial cancellation, an effective local waiver and a save-and-restart preservation case (C1, C2, C3, C4, C7).
- Only the smallest additive types and adapters those fixtures justify, starting with an outcome and a finding type mapped onto the three existing vocabularies (R5).
- Package preservation and old-client gates, before any new native document is emitted (R10, R11).
- The three-check comparator calibrated on positive and negative cases, before any suite pass is advertised (R9).
- The chart layer kind and the five route adapters incrementally, with existing tools and local offline operation retained throughout (R13, R14).
Two rules bind that order. No shared type may be frozen before the fixtures in step 2 pass (C1, C2, C3, C4, C7). The patch envelope and the source-aware diff land only after the semantics in source rows and patches and in packaging are settled, never before (plan section 18, R1). This draft states them as draft shapes and builds neither.
On 2026-10-16 Andy also decided when the shared core types may be added. DependencyGraphV1 and ComponentDefinitionV1, which plan 190 defines, and OutcomeV1 and FindingV1, which this model defines (R5), may be added to packages/core after the counterexample fixtures in step 2 pass, and not earlier. Step 3 still limits what is added then to the smallest types the fixtures justify, starting with the outcome and finding types. Until then each of the four stays a draft shape.
Completion criteria for the planning phase
| Criterion | State |
|---|---|
| Inventory and vocabulary checked against the working tree | Met, first pass; the per-format capability matrix is outstanding |
| Confirmed decisions retained without reopening them | Met |
| Remaining product choices recorded with defaults, including staged scope | Met |
| Pilot and utility examples expressed with expected outcomes | Met, as the proof cases chapter |
| Effective governance, local rejection and acceptance claims distinguished | Met |
| Fidelity, timing and editable preservation each have a testable contract | Met, one of them supported by a probe |
| Package and identity compatibility and legacy execution classifications agreed | Met |
| The counterexamples pass as contract fixtures before any shared type is frozen | Outstanding |
| Andy's answers to Q1 to Q6, or acceptance of the defaults | Met on 2026-10-16: the Q1 to Q5 defaults accepted, and Q6 decided as public |
| Specification drafting started | In progress: this draft |
Change log
| Date | Change |
|---|---|
| 2026-10-15 | Plan 315 follow-up extends wave 1 with content/metadata history, typed production bindings and refresh, stable campaign rows, action targets, explicit destination writes, readiness, search combinations and review purpose/origin. Cases 39 to 44 and focused exposure/Batch evidence are added. Affects R1, R3, R4, R5, R8, R11 and R15; no shared contract or vendor adapter is implemented. |
| 2026-10-15 | Focused DAM review and plan 314 wave 1. Four-record resource mapping, exact-byte pin requirements, source and processing authority, review subjects, imported generation evidence, fixed/adaptive delivery and private package disclosure are specified as draft requirements. Cases 30 to 38 are added. No shared type or conformance claim is introduced. |
| 2026-09-24 | Draft for review. The twelve chapters were written from the plan 276 consolidation after its final review, with D1 to D13 confirmed, R1 to R15 adopted from evidence, C1 to C9 corrected and Q1 to Q6 recorded with their defaults. No type is frozen and no conformance claim is made. |
| 2026-09-26 | Constitution. The thirteen invariants gain four reading groups with their numbers unchanged, and a table of where each one holds today, what is not met yet and which proof cases test it; the table finds no case that tests invariant 11 on its own and only case 7 behind invariant 5. The no-cloud limit now states R7 as a requirement and records that the web shell fails closed after 24 hours offline instead. The limits section says which two promises its first two items bound. Affects R7. |
| 2026-09-26 | Proof cases. Cases 24 and 25 are added for the two gaps the constitution's table found: one chart's accessibility metadata checked in each of four outputs, and a local utility that keeps no record of its run. The table now maps both, and the count of cases is 25. Q4 stays open; case 25 tests its default for a utility. Affects R5 and R15. |
| 2026-09-28 | Motion requirements from plan 281 extend values and time, packaging and proof cases. Cases 26 and 27 distinguish today's editable Lolly Design source adapter from proposed hierarchy, time mapping, writer composition and retained motion records. HTML resource closure does not imply embedded fonts in the editable package. The local pilot is evidence, not an admitted conformance suite; no shared type or container version changes. Affects R1, R10, R11, R12 and R15. |
| 2026-09-28 | Bounded scenes. Values and time records the current artboard adapter's project-time starts, frame-relative geometry, separate cameras, audio bounds and dissolve endpoint. Case 28 covers reordering and playback without treating those scenes as general nested compositions. No new source payload or package version is introduced. Affects R1, R11, R12 and R15. |
| 2026-10-07 | Learnings from plan 295, the first WebGPU and Rust kernel work. Evaluation adds kernels[] and devices[] to the receipt draft shape and a section on numerical kernels and graphics devices: an implementation revision is a result identity, host arithmetic is an environment input, a backend selection never enters an instance record, a failed implementation is never silently replaced, and renderer-owned resources belong to no record. Conformance adds graphics devices and numerical hosts to the still-image evidence: GPU output is checked within a declared band, software graphics is separate evidence, and raw floating-point identity is claimed only for import-free WebAssembly. Plan 295's phase 3 compiles Lolly Design values into drawing operations as the rendering half of the evaluation record and freezes no shared type. Affects R9 and R15. |
| 2026-10-07 | One geometry answer on every engine (plan 295, G2k). The engine geometry replaced host Math functions with V8's two-argument norm in exactly rounded operations and an embedded import-free WebAssembly module for the transcendental functions; the portable fitting kernel links the same functions. Evaluation now records that this requirement is built, and conformance gives the pinned workflow digest that Node, Chromium, Firefox and WebKit reproduce in the main realm and a worker as the example of a numerical suite. Affects R9 and R15. |
| 2026-10-07 | The rendering half of an evaluation exists in the engine as data (plan 295, phase 3, first slice). engine/src/design-draw.ts compiles Lolly Design rows into versioned drawing operations, reports every authored feature it does not carry as a finding, and freezes no shared type; the frame preview now draws through it with byte-identical output. The survey before the slice found six independent lowerings of the same rows, the cost this specification's evaluation record removes. No chapter's rules change. Affects R1 and R15. |
| 2026-10-07 | Lolly Design text and effects drawn from the evaluation (plan 295, phase 3, second and third slices). The drawing compiler follows the Lolly Design renderer, the authority on what a row means, rather than the preview's approximations, which disagree on the defaults for fields left unset. Clip, blend, shadow and blur are drawing state, and text is laid out by the engine's measure with each run's resolved face and outlined through the host from that face. A fidelity harness draws fixture pages through the real Design tool beside the compiled SVG: zero differing pixels for shapes, paths and effects, and outlined text judged run by run by ink and position, with two rejected examples on every run. Evaluation records that the operations carry each run's face, and conformance adds the measurement without setting a number. Affects R9 and R15. |
| 2026-10-07 | Pictures and the frame's own paint drawn from the evaluation (plan 295, phase 3). A picture is part of any box, fitted, positioned and zoomed as CSS does and snapped to whole pixels as Chromium snaps it; the frame paints the page with its fill, gradient, picture and border and clips its rows inside the border. The fidelity harness adds a page of pictures and two boards, all within the edge allowance (16 differing pixels on the picture page). Evaluation adds that a picture's own size and media kind are inputs the host supplies, so a receipt records each picture's digest. Affects R15. |
| 2026-10-07 | A Lolly Design page exported from the evaluation (plan 295, phase 3, P3d first slice). engine/src/design-page-svg.ts reads the authored document once and returns a frame as a self-contained SVG with outlined words and embedded pictures, plus the findings for what it does not carry. The fidelity harness now also judges the web shell's DOM walker against the Lolly Design renderer: it fails eight regions the operations pass (picture fits, pixel snapping, the frame's inner clip). Conformance records that an incumbent export is a candidate, never its own reference. Affects R9. |
| 2026-10-07 | Lolly Design SVG export drawn from the evaluation on the web and in the CLI (plan 295, P3d second slice). A frame page whose compile reports no findings is drawn from the drawing operations, and the CLI draws it with no browser; any finding sends the page to the DOM walker with the reasons stated. The web export and the Node pipeline write identical bytes on every fixture page, because hosts lend facts and the engine shapes, measures, sizes and encodes. Evaluation records the renderer choice as a declared fallback and the host interface rule that keeps shells from drifting. Affects R15. |
| 2026-10-07 | Lolly Design PDF drawn from the evaluation (plan 295, P3d third slice). The engine writes the PDF itself from the drawing operations, with no fonts because the words are outlines, and the web shell finishes it as before (print geometry, PDF/X metadata, encryption, Content Credentials); a page with shadows, blur, live text or a picture format PDF cannot embed goes to the walker with the reasons stated. Conformance records how a PDF drawn by a different rasteriser is judged against the reference, with a negative control. Affects R9 and R15. |
| 2026-10-07 | The vm execution class is built, for rondocode songs (plan 301). Values and time replaces the reserved row with what the class enforces: no host, no clock or entropy, budgets per phase, one runtime per run, refusal rather than fallback, and data out that a trusted step inspects before a fixed interpreter reads the data. Capabilities, trust and extensions declares rondocode in the draft extension shape as the unfamiliar-media check, and adds an open point for the opaque-origin frame the Sandbox utility and the patched editor run in. Case 29 covers a song that is code on web, CLI and MCP, and the constitution's table maps the case to invariants 3, 6 and 10. No shared type or schema changes. Affects R3, R10 and R15. |
| 2026-10-08 | Capabilities, trust and extensions records that the rondocode utility writes frame as the execution class of files its editor makes, the open point's default, while the point stays open. No shared type changes. Affects R15. |
| 2026-10-08 | Plan 295 extends the CLI's operations path to outlined RGB Lolly Design PDFs with the shared print and metadata finishing pass, and to SVGZ as gzip of the same SVG result. Evaluation records the detached snapshot before beforeExport, the browser's ownership of composed stories, admission findings and one complete browser fallback, fatal hook, finishing and integrity failures even with --html-fallback, and the conservative PDF/X, encryption and credential guards. Conformance records artifact readback, credential binding, AES metadata recovery, SVGZ equivalence, transport tests and a real finishing failure that writes neither PDF nor HTML. These are implementation checks; no draft receipt, released suite, global conformance or production frontend release is claimed. Affects R9 and R15. |
| 2026-10-08 | Plan 295 outlines strike-through through shared SVG/PDF drawing geometry. Evaluation records ascent from the same resolved HarfBuzz font instance and the current Lolly Design HTML reference's CSS auto policy, with unresolved metrics and underlines retained as findings. Conformance records declared decoration regions, unchanged ink/centroid bands, removed-line and shifted-line negative controls, Node/web byte parity and retained base-face refusals. Affects R9 and R15; no shared contract or production release changes. |
| 2026-10-09 | Plan 295 moves admitted Lottie vectors and flat Penpot/native PPTX primitives through internal drawing operations. Each producer keeps its existing numeric and paint reading, page selection and unsupported branches. Complete frozen producer comparisons include archive entries and resolver order; callback mutation checks preserve facts read before paint resolution and fields read later. These bounded consumers do not admit the remaining proof cases or freeze a shared evaluation type. Affects R1 and R15; no persisted schema or frontend release changes. |
| 2026-10-10 | Plan 295 extends the native PowerPoint reading to one closed, solid path contour. Evaluation distinguishes the producer's box-local EMU cubics from CSS preview geometry, keeps original callback reads and legacy branches, and records detached geometry and paint at the consumer boundary. Complete producer and archive comparisons remain separate from PowerPoint visual acceptance. Affects R1 and R15; no shared schema or authored record changes. |
| 2026-10-14 | Plan 295 P3f fills pen shapes and outlined words on the internal WebGPU raster path, after merging overlapping contours. Conformance records three references for those fills: the Lolly Design renderer within a declared band, each word's exact outline within a tight band, and Chromium's SVG as a diagnostic only, with a negative control for each limit and the rule that a reference screenshot is accepted only when two consecutive captures match. It also records that Chromium's text on Linux sat 1.08 px from the operations' layout for one italic run, a distance the drawing compiler's own harness has not measured. The path stays internal and opt-in; no export, shared type or release changes. Affects R9 and R15. |
| 2026-10-14 | Plan 295 P3f draws strokes on the internal WebGPU raster path as the fill of the region each one paints: a CSS border as the ring inside the box, and a pen stroke outlined with its cap, join and mitre limit. Conformance records the stroke rules and their controls, and a finding about the Lolly Design renderer: it offsets a pen shape's svg by its stroke pad and Chromium snaps a fractional pad, so odd round-capped widths draw 0.5 px off their geometry. The path stays internal and opt-in; no export, shared type or release changes. Affects R9 and R15. |
| 2026-10-14 | Plan 295 P3f paints linear and radial gradients on the internal WebGPU raster path over each box's own coverage, placed as CSS places a background image. Conformance records the gradient rules: shape regions keep their band, and gradient interiors must sit within 2 levels of the Lolly Design renderer, with two controls. The path stays internal and opt-in; no export, shared type or release changes. Affects R9 and R15. |
| 2026-10-14 | Plan 295 P3f draws rounded and elliptical frames on the internal WebGPU raster path and clips the rows to the box inside the frame's border. Conformance records the clip rule and its control, and that a harness judging transparent pixels must judge them over a backdrop that cannot hide a colour, such as a checkerboard. The path stays internal and opt-in; no export, shared type or release changes. Affects R9 and R15. |
| 2026-10-16 | Andy answered the six questions. The defaults for Q1 to Q5 are accepted as documented, and Q6 is recorded as decided: the specification is public from its first draft. Every chapter's Open points now state the decisions instead of open defaults. The shared core types DependencyGraphV1, ComponentDefinitionV1, OutcomeV1 and FindingV1 may be added after the counterexample fixtures pass, and not earlier. The draft notice stays on every chapter, because these answers record no reading of the chapters. Affects R5, R6, R7 and R8. |
| 2026-10-17 | Plan 295 outlines underline through the shared SVG/PDF drawing geometry. Evaluation records the reference's CSS auto placement, thickness and pixel rounding, skip-ink measured from each cluster's outline with its dilation and whole-pixel cuts, the characters drawn through, hanging spaces underlined as their own fragment, and the cases that stay a text-decoration finding. Conformance records the decorated underline page, its unchanged ink and centroid bands, and removed, moved and unskipped negative controls in SVG and PDF. Affects R9 and R15; no shared contract or production release changes. |
| 2026-10-17 | Plan 295 P3f draws dashed pen strokes on the internal WebGPU raster path, placed along the path as Chromium measures it, and clips a row by another row's silhouette draw by draw. Conformance records the dash and row clip rules and their controls, and two findings: the stroke outliner dropped a dash shorter than the stroke is wide when it outlined every dash at once, and the Lolly Design renderer draws a mirrored box's clip mirrored. The path stays internal and opt-in; no export, shared type or release changes. Affects R9 and R15. |
| 2026-10-20 | Integrates the focused DAM and controlled-production amendment from plans 314 and 315 with the later source-history evidence and Andy's six decisions. Keeps cases 30 to 44 as scoped requirements, preserves the chapter review notices and existing implementation limits, and adds no shared type or schema. Affects R1, R3, R4, R5, R7, R8, R10, R11 and R15. |
| 2026-10-26 | Lessons from OpenUSD. Source rows, payloads and patches and proof case 14 require the scene payload record to declare its length unit and its up axis, after the decision to name AR Quick Look and visionOS as USDZ targets. Capabilities, trust and extensions proposes a third requiredness class, degrades, from the OpenUSD 26.08 Profiles schema, for review, and maps the USD term profile to a conformance suite. No field or type is added. Affects R1 and R10. |
A change to any chapter must add a row here with its date and what changed, so that the chapter sources in docs/spec/document-model/ carry one history (plans/276-execution.md section 1A). A row lists the resolution ids the change affects, which is this specification's own convention.
Open points
- Q6. Whether the specification is public from the first draft. Decided on 2026-10-16: yes, published from
docs/to the/infosite, becausedocs/constraints.md,docs/determinism.mdanddocs/reproducibility.mdalready make public promises this model keeps. Evidence that would reopen it: a reason to keep the drafts private until the pilots pass. - The reading of the chapters. Still open. The notice at the head of every chapter stays until this chapter records that people have read the draft, starting with the constitution, source rows and patches, policy and conformance chapters.
The other five questions are in the answered questions table above, and each chapter they touch states the decision: Q1 and Q5 in conformance, Q2 and Q3 in policy, Q4 in operations.
Precedents
docs/constraints.mddocs/determinism.mddocs/reproducibility.mddocs/glossary.mdpackages/core/src/canvas-op-v1.tspackages/core/src/chart-v1.tspackages/core/src/design-tool-v1.tspackages/core/src/file-operation-v1.tspackages/node-shell/src/rebrand-run-manifest.tspackages/node-shell/src/content-roots.tsschemas/canvas-op.schema.jsonservices/mcp/src/tools.tsscripts/tool-requires.tsengine/src/compare.tsengine/src/runtime.tsengine/src/document-api.tsshells/web/src/lib/lolly-pack.tsshells/web/src/lib/design-system/hosted.tsshells/web/src/lib/instance-leave.tsplans/276-document-model-evidence/crdt-cycle-probe.mjs