Files

tegwick df658e7ef9 feat: TTL enforcement and operational hardening (SAND-WP-0009)

Add TTL parser, expires_at on create, extend_ttl and expire/reap APIs,
activity-core integration doc, repo classification, registry refresh,
HTTP parity, and 69 tests.

2026-06-24 12:44:04 +02:00

1.2 KiB

Raw Blame History

activity-core integration

activity-core schedules bounded work on Railiance01. sand-boxer provides sandbox venues with TTL enforcement; activity-core owns when expire runs.

Scheduled TTL reap

Run periodically (cron, Temporal activity, or CI):

sandboxer expire --apply

HTTP equivalent:

POST /v1/sandboxes/expire?apply=true

Returns a list of ExpireActionResult entries (dry-run, destroyed, failed).

Lifecycle events

Each expired sandbox emits a State Hub progress event:

state: expired (event_type: milestone)
Followed by destroying → destroyed

Event detail includes ttl, expires_at, and reachability fields.

What sand-boxer does not do

No Temporal workflows or activity-core code in this repo
No push webhook to activity-core on expiry (poll/schedule only in v0)
TTL parsing and destroy orchestration live in sand-boxer

Consumer pattern

activity-core activity provisions via sandboxer create (or HTTP)
Work runs in the sandbox (glas-harness, wise-validator, etc.)
Scheduled sandboxer expire --apply reaps past-TTL sandboxes
State Hub records full lifecycle for audit

1.2 KiB Raw Blame History