Software

Software as a living system — and a pressure test of the Atlas ontology

Two lanes, never merged

Everything below is documentation provenance: evidence that a provenance record changed. It is not runtime-capability history. Capability comparisons diff from the frozen source boundary only.

Capability baseline

7d08bfdef83c11e7ea8c10ef4ed2e16b3cb68c13

Frozen source boundary under test.

Documentation commit

b8c7f74878187d685aa0ece9aed4b469f5bbbb8c

Documentation about the boundary. Excluded from the capabilities under test.

Append-only

Documentation supplements

Observer Boundary — Direct Lovable Read Access

mem/changes/OBSERVER-BOUNDARY-2026-08-26.md

2026-08-26docs-only

Supplement 2026-08-26 (S1) — Connector-verified platform observation

Documentation-transition evidence

  • Reconciliation Lovable message ID

    lovable-message-id

    umsg_01m0yya268era9qc5rmzv4y2bn

    Does not establish: Does not establish the historical origin of Atlas or of any feature.

  • Reconciliation edit ID

    lovable-edit-id

    edt-7db970f7-8841-4a3b-b6c6-0b6378671c9c

    Does not establish: Does not establish any runtime or schema change.

  • Resulting provenance-docs commit SHA

    commit-sha

    b8c7f74878187d685aa0ece9aed4b469f5bbbb8c

    Does not establish: Is not a capability baseline; capability comparisons diff from the frozen source boundary instead.

Platform observation (connector boundary)

  • Platform internal project name

    project-id

    onsite-hero-app

    Does not establish: Does not establish an earlier or original product identity.

  • Lovable project ID

    project-id

    d387b620-9214-499c-9e87-1890a12131ad

    Does not establish: Does not establish Atlas genesis.

  • Project creation timestamp

    timestamp

    2026-05-08T21:13:28.995Z

    Does not establish: Establishes when a Lovable project was created, not when Atlas as constituted began.

Frozen capability baseline (reference only)

  • Pre-provenance-update latest_commit_sha

    commit-sha

    7d08bfdef83c11e7ea8c10ef4ed2e16b3cb68c13

    Does not establish: Does not establish when any listed capability was first implemented.

Preserved uncertainty statements

  • “Project visibility / publish status”
    The original row is a true statement about what was observable from the working tree; it may not be deleted to make the record read as if the fact was always known.
  • “No Lovable message ID, edit ID, or platform-side commit SHA is cited here, because none was inspected first-hand by this agent.”
    Retained uncertainty about the original record's evidence basis. The supplement adds later observation at a different boundary rather than rewriting this.
  • “the chain `Home Trades → HomeFlow → Atlas` is recorded as a **candidate**”
    The intermediate lineage link remains not_locatable; connector metadata did not establish it.

Corrects implication only

  • The 'not-yet-established' visibility row must no longer be read as 'not established anywhere' — visibility, publish state and platform status are now observed at the platform boundary.

Explicit non-claims

  • Not Atlas genesis.
  • Not a doctrine change.
  • Not a runtime change.
  • Not proof that anything in the application changed on 2026-08-26.

Pre-Test Checkpoint — Before Expedition Control Generalisation

mem/changes/CHECKPOINT-2026-08-26-PRE-EXPEDITION-CONTROL.md

2026-08-26docs-only

Supplement 2026-08-26 (S1) — Connector-verified platform observation

Documentation-transition evidence

  • Resulting provenance-docs commit SHA

    commit-sha

    b8c7f74878187d685aa0ece9aed4b469f5bbbb8c

    Does not establish: Documentation about the frozen boundary; excluded from the capabilities under test.

Platform observation (connector boundary)

  • Publish state

    project-id

    is_published: false

    Does not establish: Does not describe any capability present in the baseline commit.

Frozen capability baseline (reference only)

  • Pre-provenance-update latest_commit_sha

    commit-sha

    7d08bfdef83c11e7ea8c10ef4ed2e16b3cb68c13

    Does not establish: Does not establish when any listed capability was first implemented.

Preserved uncertainty statements

  • “Known vs inferred at this checkpoint”
    The section states what was observable from the working tree at checkpoint time and remains true at that boundary.
  • “The date on which Diamond ceased to be deferred is **not established** by this record”
    The transition point remains unobserved · not_locatable.
  • “Nothing in this checkpoint authorises Expedition Control or Skin OS work.”
    Scope restraint clause; removing it would widen authority silently.

Corrects implication only

  • Platform visibility and publish status are now observed; the checkpoint's source boundary is unchanged.

Explicit non-claims

  • The baseline for capability comparison remains the frozen source boundary, not the provenance-docs commit.