From c940a343c35734444386468641cd0ed1f4a2daaa Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN Date: Wed, 30 Sep 2026 15:47:38 -0400 Subject: [PATCH] Authorize bounded runtime diagnostics pilot and hourly manager checks --- .torch/prompts/COMMON.md | 48 ++++++++++++++++++++----------- .torch/prompts/session-manager.md | 5 ++-- .torch/torch.yaml | 6 ++-- 3 files changed, 39 insertions(+), 20 deletions(-) diff --git a/.torch/prompts/COMMON.md b/.torch/prompts/COMMON.md index 3fb0de4..973199d 100644 --- a/.torch/prompts/COMMON.md +++ b/.torch/prompts/COMMON.md @@ -2,22 +2,38 @@ Repository state outranks conversation memory. Query ownership before crossing a domain boundary. -## First-run owner authorization +## Owner-approved first development pilot (2026-09-30) -This initial launch is a bounded installation and communications smoke test. -Use the installed `torch` launcher and identity-bound TORCH MCP tools. Query -identity, ownership and inbox. Specialists query their next backlog item; -the Session Manager inspects fleet backlog rather than claiming specialist work. -Run `torch brief --area --json` at startup and before each new item. -Read current canonical -instructions and report the checkout HEAD in durable status. +The owner now authorizes a bounded TORCH-building-TORCH development trial, +with the outer assistant acting as arbiter through the Session Manager. This +supersedes the earlier smoke-only instruction. It is not general release authority. -Do not implement code, create or assign development tasks, enable timers, -launch other AI sessions, push branches, integrate, release or deploy during -this trial. Do not inspect credentials or alter global provider settings. -The Session Manager should read specialist check-ins and send one durable -acknowledgement. Each specialist should send one concise setup check-in to -session-manager and report idle. An empty queue is valid; finish this turn. +Use the installed `torch` launcher and identity-bound MCP tools. Re-read +`torch brief --area --json` on startup and before every new item; +canonical instructions outrank old conversation/worktree copies. Query identity, +ownership, inbox and exact current Git state; report durable evidence. -If a tool or installation boundary fails, record the exact error and stop; -do not bypass guards or invent success. Model selection is project-scoped. +First slice: TASK-conversation-runtime-diagnostics, owned by Provider Runtime. +Session Manager may triage this proposal to ready, assign it to provider-runtime, +coordinate its Release/QA boundaries and request independent review. Do not +dispatch other development items in this first pilot. The outer arbiter controls +provider starts, integration authorization and the next slice. + +The assigned specialist may implement within its owned paths, run local checks +and commit on its existing worktree branch. Ask the responsible owner before +editing shared/other-owned files. Name the task in commits, preserve all existing +work, provide regression evidence and report ready for review. No self-claim is +enabled. Resumed active work outranks another ready item; idle is valid. + +No remote push, default-main promotion, landing, package publication, deployment, +external notification, paid image/voice generation, arbitrary cleanup or global +provider configuration changes are authorized in this slice. Do not inspect +credentials. Keep pipeline work and Claude/Pi migration queued for later. + +Machine manager check-ins are owner-approved hourly with a maximum of 12 +automatic invocations per UTC day in subscription invocation-count mode (not a +dollar cap). They inspect direct reports/approval waits and report exceptions; +they must not launch specialists or expand this slice. Provider-runtime turns are +launched by the arbiter, not automatically by the manager. Do not change timers +or budgets yourself. When blocked or finished, record evidence and end the turn; +do not poll, wait indefinitely, invent filler work or bypass a failed guard. diff --git a/.torch/prompts/session-manager.md b/.torch/prompts/session-manager.md index 1b35544..b8b0bc6 100644 --- a/.torch/prompts/session-manager.md +++ b/.torch/prompts/session-manager.md @@ -9,8 +9,9 @@ At startup and when recurring cross-domain friction appears, run `torch_assess_h The owner has seeded conversation follow-up as `TASK-conversation-*` proposals in this project's existing backlog. Read `docs/TODO.md`'s authoritative current handoff and `reports/audit/conversation-handoff-2026-09-30.md` before prioritizing. -Proposed tasks are not ready assignments. The common smoke-only authorization -still applies until the owner approves a development scope, budget and startup. +Proposed tasks are not ready assignments. Read COMMON.md for the current +owner-approved pilot scope, budget and startup boundaries; older smoke-only +conversation instructions have been superseded by that explicit approval. For an empty intake, ask what the owner wants to work on first or offer a reviewed TODO import; do not invent filler work or duplicate the backlog in this document. diff --git a/.torch/torch.yaml b/.torch/torch.yaml index 98cfba4..e0adec4 100644 --- a/.torch/torch.yaml +++ b/.torch/torch.yaml @@ -120,12 +120,13 @@ "lifetime": "system", "trigger": { "type": "interval", - "seconds": 900 + "seconds": 3600 }, "behavior": "coordination", "action": { "type": "manager-check-in", - "manager_id": "session-manager" + "manager_id": "session-manager", + "wake": { "enabled": true, "budget_mode": "invocation-count" } }, "required_authority": [ "owner" @@ -137,6 +138,7 @@ "source_of_truth": "active organization direct-report graph" } ], + "runtime_wake_budget": { "max_invocations_per_day": 12 }, "integration": { "provider": "torch", "target": "rewrite/portable-agent-fleet",