Each state is kept distinct. A preceded B is never rewritten as A caused B. Competing explanations are preserved rather than pruned, and confidence reflects evidence — never how compelling the story sounds. Evidence bundles →
Possible explanations
Hypotheses
The sandbox remote and the GitHub sync are two different transports; nothing was broken by the organisation move.
favouredExplains observation
- — Sandbox origin points at Lovable private transport, which is not evidence that GitHub sync is broken. Two different transports were conflated.
Transmission path (linked automatically)
5 demonstrated routes found in the documented substrate. Influence may be inferred up to the evidence available.
- technical dependencyEndless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas contains Registry Framework → Endless-Technologies/Atlas documented by Registry Framework → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas owned by Lovable build agent → Lovable build agent is connected to Endless-Technologies/Atlas with authority "act-delegated" and declared write permission. → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas documented by Registry Framework → Endless-Technologies/Atlas contains Registry Framework → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyLovable build agent is connected to Endless-Technologies/Atlas with authority "act-delegated" and declared write permission. → Endless-Technologies/Atlas owned by Lovable build agent → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
Transmission path (declared on the record)
- technical dependencyLovable private storage is the sandbox origin by design.
Evidence
- supportingLovable sync settings show Endless-Technologies/onsite-hero-app connected. (contemporaneously documented)
If this is false, we should see
If false, pushes made through the Lovable editor would not appear on the GitHub repository.
Cheapest discriminating test
The organisation transfer broke code synchronisation and the settings page is stale.
disfavouredExplains observation
- — Sandbox origin points at Lovable private transport, which is not evidence that GitHub sync is broken. Two different transports were conflated.
Transmission path (linked automatically)
5 demonstrated routes found in the documented substrate. Influence may be inferred up to the evidence available.
- technical dependencyEndless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas contains Registry Framework → Endless-Technologies/Atlas documented by Registry Framework → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas owned by Lovable build agent → Lovable build agent is connected to Endless-Technologies/Atlas with authority "act-delegated" and declared write permission. → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas documented by Registry Framework → Endless-Technologies/Atlas contains Registry Framework → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyLovable build agent is connected to Endless-Technologies/Atlas with authority "act-delegated" and declared write permission. → Endless-Technologies/Atlas owned by Lovable build agent → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
Transmission path (declared on the record)
- account accessRepository ownership changed, which can invalidate an app installation.
Evidence
- contradictingSandbox git remote points at Lovable private transport, not at github.com. (contemporaneously documented)
- supportingLovable sync settings show Endless-Technologies/onsite-hero-app connected. (contemporaneously documented)
If this is false, we should see
If false, recent commits appear on GitHub with no manual intervention.
Cheapest discriminating test
Frozen PRs 8 and 9 belong to onsite-hero-app, not to Atlas.
openExplains observation
- — The connected repository is onsite-hero-app while the frozen pull requests were discussed as Atlas. Repository identity is unresolved.
Transmission path (linked automatically)
A route exists but every version of it rests on inferred or mocked substrate. Influence may not be raised above plausibly-linked.
- repository accessGitHub Copilot / Codex is connected to Endless-Technologies/onsite-hero-app with authority "none" (read/propose only).(route unconfirmed)
Transmission path (declared on the record)
- repository accessonsite-hero-app is the repository currently connected to this workspace.
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)
If this is false, we should see
If false, Atlas carries two open PRs numbered 8 and 9.
Cheapest discriminating test
Frozen PRs 8 and 9 belong to the Atlas repository as originally described.
openExplains observation
- — The connected repository is onsite-hero-app while the frozen pull requests were discussed as Atlas. Repository identity is unresolved.
Transmission path (linked automatically)
A route exists but every version of it rests on inferred or mocked substrate. Influence may not be raised above plausibly-linked.
- repository accessGitHub Copilot / Codex is connected to Endless-Technologies/onsite-hero-app with authority "none" (read/propose only). → Atlas contains Endless-Technologies/onsite-hero-app — Corrected 2026-08-28: onsite-hero-app is this Atlas repository's historical slug. Supersedes the earlier product.homeflow attribution, preserved in obs.repo-ambiguity. → Atlas contains Endless-Technologies/Atlas(route unconfirmed)
Transmission path (declared on the record)
- communicationThe PRs were discussed in the same messages as Atlas work.
Evidence
- neutralPull requests 8 and 9 were described as frozen, without a repository qualifier. (recollection only)
If this is false, we should see
If false, onsite-hero-app carries those PR numbers instead.
Cheapest discriminating test
Similarity is not attribution
Pattern observations
Vocabulary in this project (registry, provenance, event spine, evidence) resembles vocabulary appearing in unrelated platform documentation over the same period.
openAxes compared
- terminology: Overlapping nouns; different definitions on inspection.
- timing: Both within the same months; no ordering established.
- architecture: Not compared — no access to the other implementation.
- public release history: Not retrieved.
Explanations still on the table
Transmission path (linked automatically)
No documented communication, access, document, API interaction or dependency links external.unrelated-platform to Endless-Technologies/Atlas. Influence is withheld; the record stays an observation.
No documented communication, access, document, API interaction or dependency was found in the substrate, so no path was linked.
What communication, access grant, transmitted document, API interaction or dependency would connect external.unrelated-platform to Endless-Technologies/Atlas?
No attribution recorded. Influence is only inferred where a documented transmission path exists.
Not yet explained by the model
Anomalies
Two authoritative-looking surfaces disagreed about connection state, and the disagreement recurred across sessions.
explainedSeen 3× · priority watch · recurrence raises investigative priority only, never causal strength.
- — The sandbox remote and the GitHub sync are two different transports; nothing was broken by the organisation move.
- — The organisation transfer broke code synchronisation and the settings page is stale.
PR numbers 8 and 9 have no confirmed repository. The reference has survived unresolved.
unresolvedSeen 4× · priority elevated · recurrence raises investigative priority only, never causal strength.
- — Frozen PRs 8 and 9 belong to onsite-hero-app, not to Atlas.
- — Frozen PRs 8 and 9 belong to the Atlas repository as originally described.
Only when justified
Attributions
The apparent disconnection was a conflation of two transports, not a broken sync.
Actor
Transmission path (linked automatically)
5 demonstrated routes found in the documented substrate. Influence may be inferred up to the evidence available.
- technical dependencyEndless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas contains Registry Framework → Endless-Technologies/Atlas documented by Registry Framework → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas owned by Lovable build agent → Lovable build agent is connected to Endless-Technologies/Atlas with authority "act-delegated" and declared write permission. → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyEndless-Technologies/Atlas documented by Registry Framework → Endless-Technologies/Atlas contains Registry Framework → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
- technical dependencyLovable build agent is connected to Endless-Technologies/Atlas with authority "act-delegated" and declared write permission. → Endless-Technologies/Atlas owned by Lovable build agent → Endless-Technologies/Atlas depends on GitHub (Endless-Technologies org)(demonstrated)
Temporal posture: contemporaneous
Precedence: The organisation move preceded the confusion. Precedence is recorded; it is not treated as the cause.
Resolved at
Ownership of frozen PRs 8 and 9.
Actor
Transmission path (linked automatically)
A route exists but every version of it rests on inferred or mocked substrate. Influence may not be raised above plausibly-linked.
- repository accessGitHub Copilot / Codex is connected to Endless-Technologies/onsite-hero-app with authority "none" (read/propose only).(route unconfirmed)
Temporal posture: unknown
Precedence: Connection to onsite-hero-app was observed after the PRs were mentioned.
Resolved at