From 63a13fff5067b64d945c20251b682ab35a033520 Mon Sep 17 00:00:00 2001 From: thePR0M3TH3AN Date: Sat, 3 Oct 2026 01:20:40 -0400 Subject: [PATCH] TASK-conversation-documentation-current: correct continuation limits --- README.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index cae7605..637cc18 100644 --- a/README.md +++ b/README.md @@ -122,9 +122,12 @@ it is not permanent installer-owned provisioning and is not the older system-schedule framework. That framework's automatic manager wakes remain disabled. Continuation is explicitly enabled for the existing roster, dedupes unchanged signals, holds a physical turn guard per identity, and caps attempts at -12 turns per UTC day. This is a turn cap, not dollar or token governance, and -failed or interrupted attempts count. The transient timer does not survive a -host reboot. Permanent timer installation/removal, upgrade and reboot +48 turns per UTC day, with concurrency configured for up to seven turns. Twelve +earlier attempts remained charged when the daily cap was raised. These are +configured limits, not evidence that seven identities are currently active or +running. This is a turn cap, not dollar or token governance, and failed or +interrupted attempts count. The transient timer does not survive a host reboot. +Permanent timer installation/removal, upgrade and reboot qualification remain open, as do general first-install/init automation, deeper candidate-engine, execution-fence and private-admission assurance; pipeline execution and dashboard/served-provenance work; live UX review; stable