Software

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

A bundle answers one claim in full: here is what existed first, here is when it existed, here is what happened later, here are the competing explanations, here is what the evidence supports, and here is what remains unknown. If something extraordinary is happening, refusing to overstate it is what makes it credible.

Preserve → separate → compare → challenge → verify

Evidence bundles

Frozen pull requests 8 and 9 belong to onsite-hero-app.

correlated

Earliest provenance

Conversation reference, 2026-08-22observed

Chain

Event→Observation→Hypothesis→Evidence→Attribution→Confidence
  1. Event4

    2026-08-22 02:00 contemporaneous Atlas repository moved to the organisation.

    2026-08-22 05:00 contemporaneous GitHub App reinstalled at organisation level.

    2026-08-22 06:00 contemporaneous Sync settings show onsite-hero-app connected.

    2026-08-22 06:40 retrospective match PR numbers matched to the connected repository.

  2. Observation2

    anomaly Two authoritative-looking surfaces disagreed about connection state, and the disagreement recurred across sessions.

    anomaly PR numbers 8 and 9 have no confirmed repository. The reference has survived unresolved.

  3. Hypothesis4

    favoured The sandbox remote and the GitHub sync are two different transports; nothing was broken by the organisation move.

    disfavoured The organisation transfer broke code synchronisation and the settings page is stale.

    open Frozen PRs 8 and 9 belong to onsite-hero-app, not to Atlas.

    open Frozen PRs 8 and 9 belong to the Atlas repository as originally described.

  4. Evidence3

    supporting Lovable sync settings show Endless-Technologies/onsite-hero-app connected. (contemporaneously documented)

    neutral Pull requests 8 and 9 were described as frozen, without a repository qualifier. (recollection only)

    missing A direct listing of open PRs on both candidate repositories. (unresolved)

  5. Attribution2

    contemporaneous Lovable sandbox transport design

    The organisation move preceded the confusion. Precedence is recorded; it is not treated as the cause.

    unknown Actor unknown — status unknown

    Connection to onsite-hero-app was observed after the PRs were mentioned.

  6. Confidence1

    correlated Strength of evidence only, never narrative intensity.

Stages are ordered as states of knowledge, not as a causal sequence. A preceding stage does not cause the next, and precedence within the event rail does not establish influence.

Timeline

  • 2026-08-22 02:00 contemporaneous
    Atlas repository moved to the organisation.
  • 2026-08-22 05:00 contemporaneous
    GitHub App reinstalled at organisation level.
  • 2026-08-22 06:00 contemporaneous
    Sync settings show onsite-hero-app connected.
  • 2026-08-22 06:40 retrospective match
    PR numbers matched to the connected repository.

Order is recorded. Order alone does not establish influence.

Evidence

  • supportingLovable sync settings show Endless-Technologies/onsite-hero-app connected. (contemporaneously documented)
  • neutralPull requests 8 and 9 were described as frozen, without a repository qualifier. (recollection only)
  • missingA direct listing of open PRs on both candidate repositories. (unresolved)

Strongest alternative explanation

Frozen PRs 8 and 9 belong to the Atlas repository as originally described.

Strongest support

Lovable sync settings show Endless-Technologies/onsite-hero-app connected.

Strongest contradiction

Pull requests 8 and 9 were described as frozen, without a repository qualifier.

Missing evidence

Open PR listing for Endless-Technologies/AtlasOpen PR listing for Endless-Technologies/onsite-hero-appOriginal message containing a PR link

Best next verification step

Link the GitHub connector and list open PRs on both repositories.

External vocabulary resembling this project's ontology was influenced by it.

recorded

Earliest provenance

mem/doctrine — dated doctrine files precede the observationdeclared

Chain

Event→Observation→Hypothesis→Evidence→Attribution→Confidence
  1. Event2

    2026-08-21 00:00 prediction Preserve the Path doctrine committed.

    2026-08-22 22:30 retrospective match External similarity noticed.

  2. Observation0

    Nothing yet noticed across these events beyond the record itself.

  3. Hypothesis0

    No explanation proposed. The observation stands unexplained.

  4. Evidence1

    supporting Preserve the Path doctrine was written and committed before the Software Hub was requested. (contemporaneously documented)

  5. Attribution0

    Attribution unresolved. No actor is named.

  6. Confidence1

    recorded Strength of evidence only, never narrative intensity.

Stages are ordered as states of knowledge, not as a causal sequence. A preceding stage does not cause the next, and precedence within the event rail does not establish influence.

Timeline

  • 2026-08-21 00:00 prediction
    Preserve the Path doctrine committed.
  • 2026-08-22 22:30 retrospective match
    External similarity noticed.

Order is recorded. Order alone does not establish influence.

Evidence

  • supportingPreserve the Path doctrine was written and committed before the Software Hub was requested. (contemporaneously documented)

Strongest alternative explanation

Unknownnot yet declaredIndependent invention has no hypothesis record yet.

Strongest support

Preserve the Path doctrine was written and committed before the Software Hub was requested.

Strongest contradiction

Unknownnever existedNo contradictory evidence gathered.

Missing evidence

Any credible transmission path: communication, access, transmitted document or shared collaboratorDated public release history of the compared material

Best next verification step

Establish whether any transmission path exists at all. Without one, influence cannot be inferred and the pattern stays an observation.