Ting/CurryComb

Watch

Fork 0

OD-2: temporal model — which relations are bitemporal #35

New issue

Open

opened 2026-09-02 07:55:44 +00:00 by larandar · 2 comments

larandar commented

2026-09-02 07:55:44 +00:00

Owner

Question

Which relations need valid-time + observed-time (bitemporal) semantics instead of simple assertion/retraction timestamps?

Where this already lives

docs/handoff.md §Open decisions 2; ADR-0001 §Open decisions (temporal model); §Minimal shared relation model ("valid-time and observed-time facts where needed").

Decision procedure

Name the relation list (or "none beyond assertion/retraction") in an ADR append. Facts and curation state have provenance timestamps already; the question is about validity intervals.

Unblocks

#20 schema fields; #28 projection relations where needed.

## Question Which relations need valid-time + observed-time (bitemporal) semantics instead of simple assertion/retraction timestamps? ## Where this already lives `docs/handoff.md` §Open decisions 2; ADR-0001 §Open decisions (temporal model); §Minimal shared relation model ("valid-time and observed-time facts where needed"). ## Decision procedure Name the relation list (or "none beyond assertion/retraction") in an ADR append. Facts and curation state have provenance timestamps already; the question is about *validity* intervals. ## Unblocks #20 schema fields; #28 projection relations where needed.

larandar referenced this issue

2026-09-02 07:56:00 +00:00

Rule: the seven open design decisions #41

larandar added the

Kind/Documentation

Status/Need More Info

labels

2026-09-02 07:59:22 +00:00

larandar added a new dependency

2026-09-02 07:59:41 +00:00

#41 Rule: the seven open design decisions

larandar commented

2026-09-02 08:00:32 +00:00

Author

Owner

Grooming state: Open — owner ruling required.
Evidence: Related mentions: docs/handoff.md §Open decisions 2; ADR-0001 §Open decisions (temporal model); §Minimal shared relation model. Consumers on this tracker: #20 (schema fields), #28.
Larandar: Decision required.

**Grooming state:** Open — owner ruling required. **Evidence:** Related mentions: `docs/handoff.md` §Open decisions 2; ADR-0001 §Open decisions (temporal model); §Minimal shared relation model. Consumers on this tracker: #20 (schema fields), #28. **Larandar:** Decision required.

larandar commented

2026-09-02 08:47:04 +00:00

Author

Owner

Question: Which relations require valid-time plus observed-time semantics rather than assertion and retraction timestamps?
Decision procedure: Name the relation list, or state none beyond assertion and retraction, in an ADR append; distinguish validity intervals from existing provenance timestamps.
Consumers: #20 schema fields and #28 projection relations.
Sources: CurryComb#35 body; docs/handoff.md Open decisions 2; ADR-0001 Open decisions and Minimal shared relation model; audit 2026-09-19/20 G43.
State: The issue body remains the full record; this comment is the current projection, not a promise of future replacement.

**Question:** Which relations require valid-time plus observed-time semantics rather than assertion and retraction timestamps? **Decision procedure:** Name the relation list, or state none beyond assertion and retraction, in an ADR append; distinguish validity intervals from existing provenance timestamps. **Consumers:** #20 schema fields and #28 projection relations. **Sources:** CurryComb#35 body; docs/handoff.md Open decisions 2; ADR-0001 Open decisions and Minimal shared relation model; audit 2026-09-19/20 G43. **State:** The issue body remains the full record; this comment is the current projection, not a promise of future replacement.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#41 Rule: the seven open design decisions

Ting/CurryComb

Reference

Ting/CurryComb#35

No description provided.

Rows
Columns