Discovery — Miami Temp-Alert Agent Build Engagement — v0.1

Version. 0.1 Date. 2026-08-16 Status. Discovery document for Stage 1 of the agent-commissioning chain. Input to the Phase 53 upload → extract → induct route. Authored by Claude for Operator approval (approval is the Stage 1 kickoff). Companions. loomworks-agent-commissioning-chain-note-v0_1.md (the chain this walks); miami-temp-alert-candidate-seed-v0_5.md (the commissioning request's content — the requested agent); CR-2026-222 (Stage 2, halted pending this engagement).

Plain-language summary

This Discovery stands up Engagement 2 of the agent-commissioning chain: an engagement whose work is building the Miami temperature-alert agent — accumulating its requirements as Memory and producing the artifacts a downstream production system needs to build and operate it. The engagement does not run the agent, and at creation it renders only a requirements digest; the agent-specification output form is expected to be declared later by seed amendment, which is deliberate — that amendment is Stage 2's walk.

What the work is

Receiving a commissioning request for a monitoring agent — the Miami temperature-alert agent, as described in the request material — and carrying that request to a buildable state: accumulating the agent's requirements, decisions, and open questions as Memory with provenance to the request material; organizing and shaping that knowledge for a downstream builder; and producing the build artifacts that builder consumes. The requested agent, in brief, per the request material: a continuously maintained monitor that checks the current temperature in Miami, Florida and sends an SMS via Twilio to a designated recipient whenever the reading exceeds 90°F, operating under two-layer identity (durable Loomworks Identity above per-incarnation Stele lease), FORAY emission with a declared batch interval, supervised shutdown, and blinded liveness and drift observation.

This engagement builds toward that agent. It does not execute it. Where the agent runs, and under whose supervision, is committed in the request material (a supervised process on Operator infrastructure), not in this engagement.

Who consumes the work

• The Operator (Marvin Percival): requirements digests, build progress, open-question status.
• A downstream production system: the eventual consumer of the engagement's build artifacts, once the output form for that consumer is declared. At creation, no render-type addresses this consumer; the declaration is expected to arrive by seed amendment when the output form is settled.

Voice

Plain, exact, build-oriented. Requirements stated as testable commitments; open questions named as open, never smoothed into assumptions.

Constraints

• Source discipline. Requirements enter Memory with provenance to the commissioning request material (miami-temp-alert-candidate-seed-v0_5.md and its companions). Nothing is fabricated beyond the request; gaps in the request are recorded as open questions, not filled silently.
• Open items are work, not blockers. The request's known open items — de-duplication rule, check cadence, weather data source, Stele lease mechanism, supervisor scope, observer specifications, creation/closure event schemas — are requirements this engagement resolves during the build, each resolution recorded with its reasoning.
• Execution boundary. This engagement produces build artifacts; it never executes the agent and never becomes its runtime.
• Corrections preserved. Superseded requirements remain as corrections; the request material's own trajectory notes (v0.1 through v0.5) enter Memory as prior positions where relevant.
• Amendment discipline. Changes to this engagement's seed follow the versioned-supersession ceremony: declared class, Operator commit, prior versions preserved.

Success conditions

• Every requirement of the requested agent is in Memory with provenance to the request material or to a recorded resolution of a named open item.
• A downstream builder can construct and operate the agent from this engagement's rendered artifacts alone, without reading Memory directly.
• No open item from the request is lost: each is either resolved with its reasoning recorded, or still visibly open.

Initial contributors

• Operator: Marvin Percival. Governs, resolves open items, holds all seed amendments and artifact state transitions.
• Companion: drafts, organizes, and shapes; contributions marked as Companion-origin.
• No other contributors at creation.

Declared render-types

• Requirements digest — document — Mode A (Loomworks-produced) — consumer: the Operator — the current state of the requested agent's requirements and open items, organized for review.

(The build-artifact render-type for the downstream production system is deliberately not declared at creation; it is expected to be added by seed amendment when the output form is settled.)

Authorisation

The Operator governs. The Companion contributes and drafts but holds no authority over the seed, artifact states, or open-item resolutions. Seed changes only through the amendment ceremony under Operator commit.

Done In Seven LLC — DUNIN7 Discovery — Miami Temp-Alert Agent Build Engagement — v0.1 — 2026-08-16