Ting/CurryComb

Watch

Fork 0

OD-6: rule ownership — canonical home for the shared schema and resolver #39

New issue

Open

opened 2026-09-02 07:55:45 +00:00 by larandar · 3 comments

larandar commented

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

Owner

Question

Which repository or crate is the canonical home of the shared value/relation schema and the deny-biased resolver, while application rules stay local to each service?

Where this already lives

docs/handoff.md §Open decisions 6; §Datalog unification ("Rules remain reviewed source files in repositories"); §Migration proof step 1 ("small Rust crate").

Decision procedure

Name the home (a CurryComb crate, a lar.ad crate, or a Tier-2 estate crate) in an ADR append, citing the dependency direction: Jostoph, Vedanta, and CurryComb all consume it without a shared central database.

Unblocks

#20 placement; #21's landing crate; #32.

## Question Which repository or crate is the canonical home of the shared value/relation schema and the deny-biased resolver, while application rules stay local to each service? ## Where this already lives `docs/handoff.md` §Open decisions 6; §Datalog unification ("Rules remain reviewed source files in repositories"); §Migration proof step 1 ("small Rust crate"). ## Decision procedure Name the home (a CurryComb crate, a `lar.ad` crate, or a Tier-2 estate crate) in an ADR append, citing the dependency direction: Jostoph, Vedanta, and CurryComb all consume it without a shared central database. ## Unblocks #20 placement; #21's landing crate; #32.

larandar referenced this issue

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

Rule: the seven open design decisions #41

larandar referenced this issue

2026-09-02 07:57:47 +00:00

Shared value + relation schema crate: typed values replace Jostoph Atom #20

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:42 +00:00

#41 Rule: the seven open design decisions

larandar added a new dependency

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

#32 Slice 6 — Datalog dialect migration

larandar commented

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

Author

Owner

Grooming state: Open — owner ruling required.
Evidence: Related mentions: docs/handoff.md §Open decisions 6, §Datalog unification, §Migration proof 1. #20 ships locally pending the move; #21's landing crate is this decision's output; gated session #32.
Projection: The current store is Ting/contracts; the ting-wiki store was retired in the grooming-log entry dated 2026-09-04. The canonical crate and home remain the unresolved OD-6 decision.
Audit: G6, grooming audit 2026-09-19/20.
Larandar: Decision required.

**Grooming state:** Open — owner ruling required. **Evidence:** Related mentions: `docs/handoff.md` §Open decisions 6, §Datalog unification, §Migration proof 1. #20 ships locally pending the move; #21's landing crate is this decision's output; gated session #32. **Projection:** The current store is `Ting/contracts`; the `ting-wiki` store was retired in the grooming-log entry dated 2026-09-04. The canonical crate and home remain the unresolved OD-6 decision. **Audit:** G6, grooming audit 2026-09-19/20. **Larandar:** Decision required.

larandar commented

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

Author

Owner

Question: Which repository or crate is the canonical home of the shared value and relation schema and deny-biased resolver while application rules stay local?
Decision procedure: Name the home in an ADR append and cite dependency direction so Jostoph, Vedanta, and CurryComb can consume it without a shared database. The current store is Ting/contracts; the canonical crate and home remain the OD-6 decision.
Consumers: #20 placement, #21 landing crate, and #32.
Sources: CurryComb#39 body; docs/handoff.md Open decisions 6, Datalog unification, and Migration proof 1; 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 repository or crate is the canonical home of the shared value and relation schema and deny-biased resolver while application rules stay local? **Decision procedure:** Name the home in an ADR append and cite dependency direction so Jostoph, Vedanta, and CurryComb can consume it without a shared database. The current store is Ting/contracts; the canonical crate and home remain the OD-6 decision. **Consumers:** #20 placement, #21 landing crate, and #32. **Sources:** CurryComb#39 body; docs/handoff.md Open decisions 6, Datalog unification, and Migration proof 1; 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.

codexo referenced this issue

2026-09-02 15:05:37 +00:00

Epic: council-safe Session materialisation #48

codexo commented

2026-09-02 15:16:35 +00:00

Contributor

Shared OpenSpec projection

Root Campaign: Ting/Ting#83
Store: ting-wiki
Change: agentic-software-delivery-loop
Commit: pending wiki Git publication; this is a hard readiness gate
Selected requirements: GD-4, CG-3, SE-1 through SE-3
Projected work: authority/projection Session #47; OD-6 remains the schema-home gate

This comment does not ratify or reopen settled local design. It binds this existing work to the shared contract and its named scenarios. Keep new projected work in Status/Need Grooming until the immutable Store commit and strict validation evidence are recorded.

Authored through the Ting Forge connector as codexo; independent review remains required.

## Shared OpenSpec projection - Root Campaign: Ting/Ting#83 - Store: `ting-wiki` - Change: `agentic-software-delivery-loop` - Commit: pending wiki Git publication; this is a hard readiness gate - Selected requirements: GD-4, CG-3, SE-1 through SE-3 - Projected work: authority/projection Session #47; OD-6 remains the schema-home gate This comment does not ratify or reopen settled local design. It binds this existing work to the shared contract and its named scenarios. Keep new projected work in Status/Need Grooming until the immutable Store commit and strict validation evidence are recorded. _Authored through the Ting Forge connector as `codexo`; independent review remains required._

codexo referenced this issue

2026-09-02 15:26:08 +00:00

docs: bind CurryComb beneath ratified council output #49

No milestone

No project

No assignees

2 participants

Notifications

Due date

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

No due date set.

Blocks

#32 Slice 6 — Datalog dialect migration

Ting/CurryComb

#41 Rule: the seven open design decisions

Ting/CurryComb

Reference

Ting/CurryComb#39

No description provided.

Rows
Columns