LLP 0086-0092: automatic projection of derived datasets (design)#279
Draft
philcunliffe wants to merge 1 commit into
Draft
LLP 0086-0092: automatic projection of derived datasets (design)#279philcunliffe wants to merge 1 commit into
philcunliffe wants to merge 1 commit into
Conversation
Design set making automatic graph projection the default (opt-out via config), superseding LLP 0023 section on-demand-projection for the default trigger only. The rest of LLP 0023 (contracts, ids, merge, dedup, compaction) stands and is what makes automatic re-projection idempotent. - 0086 spec: automatic derivation requirements (default-on, opt-out, bounded, eventually fresh, general; cost/exfiltration derivations stay opt-in) - 0087 decision: automatic projection is the default - 0088 decision: scheduled daemon tick as the trigger (not a commit hook) - 0089 decision: bounded, isolated execution (answers 0023's OOM objection) - 0090 decision: general derivation registration seam - 0091 design: registry seam, daemon tick loop, derive config block - 0092 plan: implementation steps - 0023: superseded-by note on the on-demand-projection default Docs only; no code changes. Implementation is LLP 0092. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Design-only LLP set (no code) that makes automatic graph projection the default, with a config opt-out, and generalizes the mechanism to "things like the graph."
Today the T0 activity graph only projects when someone runs
hyp graph project(LLP 0023 §on-demand-projection), so a running install accumulates capture while its graph silently drifts stale. This set reverses that default.Why it's safe to reverse LLP 0023
LLP 0023 kept projection out of the daemon because it "could block or OOM the daemon." The daemon already runs bounded background work safely: the cache-maintenance loop (
runtime.js) is default-on/opt-out, interval-driven, budget-capped, single-flight, and error-isolated. Automatic projection rides that same shape, so the objection is answered without inventing a kernel commit hook.The documents
ctx.derivations.register;defaultOnper-derivation so enrichment stays off)deriveconfig block, what the graph registersPlus a superseded-by note on LLP 0023 §on-demand-projection; the rest of 0023 (contracts, content-addressed ids, merge, dedup, compaction) stands and is what makes automatic re-projection idempotent.
Scope / status
Status: Draftfor review before Accepted, since this reverses an Active decision.@refs, LLP numbers, section anchors, and repo paths verified to resolve.Notable defaults (flag if you disagree)
graph compactstays manual this slice; auto-compaction is a listed follow-on.🤖 Generated with Claude Code