jason.woltje
193479b52d
Mosaic concepts pages now own the adapted content; source/license metadata under docs/reference/concepts. Adds ACT-1 agent-context planning capture, pinned concept test package + preparation utility, foundation observation notes (durability, evidence, federation, onboarding, workflow), and the #1495 consolidation assessment. TOOLS.md updated for the host-dev launcher.
2.1 KiB
Standing intents and future obligations
Status: proposed event-obligation concept, separate from the existing goal extension. No event matcher or new scheduler is introduced here.
| Request | Appropriate record |
|---|---|
| Do something at a stated time | An authorized scheduled task |
| React when a specific event occurs | A scoped event obligation |
| Improve something over time | An assignment or reviewed aspiration |
| Continue an active bounded outcome | The existing goal/work lifecycle |
Writing any of these in prose does not register a wake mechanism.
Proposed event record
Identify the owner, authorized action, target scope, trigger, source event, creation authority, expiry, firing limit, cancellation state and evidence destination. Verify that a real event-delivery mechanism owns the wake before promising unattended continuation.
Match and deduplicate within deterministic scope and lifecycle rules. A model may interpret an event where authorized, but it must not invent missing permission, expand the audience, or retry an uncertain external effect automatically.
Delivery and cancellation
Distinguish registered, triggered, delivered, acted upon and completed. A fired trigger is not proof that the requested action succeeded. Reconcile before restarting interrupted work; do not duplicate an action merely because its receipt has not arrived.
Cancellation is durable and explicit. Expiry, cooldown and firing budgets bound repetition; exact limits are policy decisions rather than universal constants. Notification delivery does not clear a pause or authorize unrelated work.
Mosaic's native goal extension has its own process-incarnation behavior and supported waits. This concept must integrate with that ownership instead of introducing a second goal loop. The operator can still use manual reconciliation when no authorized automatic wake exists.
ACT-C10 tests classification and honest wake claims. Runtime tests must cover scope, duplicate events, expiry, cancellation and restart recovery. See state awareness and goal extension.