Software

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

Registry explorer

Should Atlas absorb HomeFlow?

dec.separate-repos

Decisions

Should Atlas absorb HomeFlow? Atlas is the orchestration layer; HomeFlow is the product layer. Keep separate with documented contracts Integration happens through atlas-entity/v1, atlas-event/v1 and atlas-knowledge/v1 only.

decisionsreleasedcostly

Platform

not declared

Licence

undeclared

Declared date

2026-08-19

Category listing

Open Decisions

Read only

Declared record

Fields and provenance

at

2026-08-19observed · scope note

question

Should Atlas absorb HomeFlow?

context

Atlas is the orchestration layer; HomeFlow is the product layer.

optionsConsidered

  • Merge repositories
  • Keep separate with documented contracts

chosen

Keep separate with documented contractsdeclared · mem/features/deferred-atlas-scope.md

rejected

  • Merge repositories

evidence

  • Boundary discipline in workspace doctrine

constraintIds

  • con.scope-boundary
  • con.no-pii

consequence

Integration happens through atlas-entity/v1, atlas-event/v1 and atlas-knowledge/v1 only.declared · src/contracts

reversibility

costly

responsibleParty

Stewarddeclared · scope note

linkedEventIds

none declared

linkedObservationIds

  • obs.repo-ambiguity

reassessment

Unknown · not-yet-declared

lifecycle

released

Relationships

Declared edges

0

No relationships declared for this entry yet.

Evidence chain

What this entry rests on

Events

0

None declared for this entry.

Observations

0

None declared for this entry.

Decisions

1
  • dec.separate-repos — released · Should Atlas absorb HomeFlow?

Constraints

0

None declared for this entry.

Changes

1
  • chg.release-1 — release · Release 1 · Doctrine compilation and release gate

Open questions

0

None declared for this entry.