How should software data that Atlas cannot yet observe be represented?
dec.mocked-labelling
How should software data that Atlas cannot yet observe be represented? Live GitHub, registry and deployment data is not connected to this surface. Typed absence with explicit unknown reasons Every registry card can show Unknown as an inspectable state and generate a question.
Read only
Declared record
Fields and provenance
at
question
context
optionsConsidered
- Plausible placeholder values
- Empty states
- Typed absence with explicit unknown reasons
chosen
rejected
- Plausible placeholder values
- Empty states
evidence
- Preserve the Path doctrine
- C17 absence kinds
constraintIds
- con.no-fabrication
consequence
reversibility
responsibleParty
linkedEventIds
- evt.software-hub
linkedObservationIds
reassessment
lifecycle
Relationships
Declared edges
No relationships declared for this entry yet.
Evidence chain
What this entry rests on
Events
0None declared for this entry.
Observations
0None declared for this entry.
Decisions
1- dec.mocked-labelling — released · How should software data that Atlas cannot yet observe be represented?
Constraints
0None declared for this entry.
Changes
0None declared for this entry.
Open questions
0None declared for this entry.