C1: The curation rules module #46

New issue

Open

opened 2026-08-12 16:15:42 +00:00 by agent.teyla · 0 comments

agent.teyla commented

2026-08-12 16:15:42 +00:00

Contributor

M2 frontier

In scope

src/curation.rs: an ascent! program over the fact store.
Link rules: shared focused ticket (hub-guarded); shared narrow perimeter within a locality window (sweep-guarded); adjacency glue.
contains-style BYODS trrel for component reachability — no hand-written closure rule, same reason as standing.
Derived: epic(rep, member), epic_size, standalone.

Out of scope

Findings (C3) and the CLI (C4). This issue is the derivation only.
Incremental maintenance. The thresholds are non-monotonic; recompute from the log on demand and keep the engine simple.

Boundary

Rule logic in Rust, thresholds in parameters — the policy.rs split, exactly. No constant appears in the rules.

Acceptance

Golden test: the flake-ops 61-commit corpus (checked in as fixture facts) derives the known 16 components.

Source: JOSTOPH-BACKLOG.md, Epic 2.1.

`M2` `frontier` **In scope** - `src/curation.rs`: an `ascent!` program over the fact store. - Link rules: shared focused ticket (hub-guarded); shared narrow perimeter within a locality window (sweep-guarded); adjacency glue. - `contains`-style BYODS `trrel` for component reachability — no hand-written closure rule, same reason as standing. - Derived: `epic(rep, member)`, `epic_size`, `standalone`. **Out of scope** - Findings (C3) and the CLI (C4). This issue is the derivation only. - Incremental maintenance. The thresholds are non-monotonic; recompute from the log on demand and keep the engine simple. **Boundary** - Rule logic in Rust, thresholds in parameters — the policy.rs split, exactly. No constant appears in the rules. **Acceptance** - Golden test: the flake-ops 61-commit corpus (checked in as fixture facts) derives the known 16 components. Source: JOSTOPH-BACKLOG.md, Epic 2.1.