From 0e57a0e2a78f3ad5dea27f6857912e87b7bd0150 Mon Sep 17 00:00:00 2001 From: David Baity <158404677+MazakTheDwarf@users.noreply.github.com> Date: Tue, 10 Mar 2026 19:09:48 -0400 Subject: [PATCH] =?UTF-8?q?Sprint=2053b:=20Fix=20gaps=201=20and=204=20?= =?UTF-8?q?=E2=80=94=20full=20task=20type=20coverage=20and=20charter=20ame?= =?UTF-8?q?ndment=20process?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Gap 1 — planning.yml VALID TASK TYPES expanded: Added: write_charter, market_intelligence, portfolio_architectural_review, audit_tenant, charter_audit, financial_audit, capital_allocation_audit, retire_tenant, adjudicate_tenant All governance templates now reachable from board planning sessions. Gap 4 — amend_charter template created (Valerius): Operator-only constitutional amendment process for the master CL charter. Enforces all 4 §12 criteria (identity preservation, anti-sprawl, clarity, authority). Pass threshold: 98 — highest in the system. Produces formal amendment proposal; operator must manually apply to charter.md. Agents cannot self-authorize charter changes. Valerius agent.yml updated: added amend_charter to supported_templates. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- agents/valerius/agent.yml | 1 + templates/amend_charter.yml | 116 ++++++++++++++++++++++++++++++++++++ templates/planning.yml | 24 ++++++-- 3 files changed, 135 insertions(+), 6 deletions(-) create mode 100644 templates/amend_charter.yml diff --git a/agents/valerius/agent.yml b/agents/valerius/agent.yml index dc19fc1..79c6652 100644 --- a/agents/valerius/agent.yml +++ b/agents/valerius/agent.yml @@ -18,5 +18,6 @@ department: executive supported_templates: - adjudicate_tenant - charter_audit + - amend_charter - boardroom - planning \ No newline at end of file diff --git a/templates/amend_charter.yml b/templates/amend_charter.yml new file mode 100644 index 0000000..c8b1c2b --- /dev/null +++ b/templates/amend_charter.yml @@ -0,0 +1,116 @@ +name: amend_charter +description: "OPERATOR-ONLY — Valerius drafts a formal constitutional amendment to the Crimson Leaf master charter. Adjudicated at 98. Operator must manually apply the approved amendment to charter.md." +debug: true +system: agent_prompt + +agent_prompt: + - "= identity.md" + +skills: + - guides/CorporateCharterGuide.md + +sections: + - agent + - project + - rag + - roster + - skills + - deliverables + - message + - instructions + +steps: + - type: think + hint: | + You are {agent.name}, Chief Governance Officer of Crimson Leaf LLC. + + This is a constitutional act. You are drafting an amendment to the master charter — + the foundational law of the entire Organization. This document governs every agent, + every Tenant, and every Genesis action. It cannot be changed casually. + + IMPORTANT: You are producing a PROPOSAL only. No amendment takes effect until the + Operator reviews, approves, and manually commits it to charter.md. Your role is to + draft the amendment in strict constitutional form and subject it to the §12 test. + + The operator has requested this amendment. Their exact request is in the MESSAGE section. + + Apply the §12 Amendment Standard — ALL FOUR criteria must be satisfied: + + 1. IDENTITY PRESERVATION + Does this amendment preserve Crimson Leaf's identity as the Genesis Node and holding company? + Would any aspect of this amendment cause Crimson Leaf to drift toward becoming an + operating company, service provider, or execution entity? + PASS or FAIL — explain specifically. + + 2. ANTI-SPRAWL TEST + Does this amendment avoid reintroducing operational sprawl? + Does it add vague or expansive powers that could be abused? + Does it weaken any existing constraint without replacing it with an equal or stronger one? + PASS or FAIL — explain specifically. + + 3. CONSTITUTIONAL CLARITY TEST + Does this amendment strengthen constitutional clarity? + Is the new or revised language more precise, enforceable, and unambiguous than what it replaces? + Would the adjudicator be able to evaluate compliance against the amended text? + PASS or FAIL — explain specifically. + + 4. ELEVATED GOVERNANCE REVIEW + Is this amendment being proposed through the proper constitutional path? + Is it being triggered by the Operator (the only authorized party to amend the master charter)? + PASS or FAIL — explain specifically. + + If ANY of the four criteria FAIL, the amendment must be rejected or redesigned. + A failing amendment that still gets packaged will be rejected at 98% adjudication threshold. + + If all four criteria PASS, draft the complete amended charter section(s): + - State exactly which section(s) are being amended (by number and title) + - Show the CURRENT text being replaced (quote it exactly) + - Show the PROPOSED replacement text + - State the constitutional rationale in one precise paragraph + - State what risk or gap this amendment corrects + + - type: document + filename: charter_amendment + + - type: package + packet_type: CharterAmendmentProposal + hint: | + Serialize the amendment proposal. This is the formal constitutional record. + Do not summarize or abbreviate — every field must be complete. + The operator will use this output to manually apply the change to charter.md. + schema: + actions: + - type: quick + amendment_title: "string — short title for this amendment (e.g. 'Add §13 Emergency Governance Path')" + sections_affected: ["string — section numbers and titles being amended or added"] + identity_preservation: "string — PASS or FAIL with explanation" + anti_sprawl_test: "string — PASS or FAIL with explanation" + constitutional_clarity: "string — PASS or FAIL with explanation" + elevated_governance: "string — PASS or FAIL with explanation" + overall_verdict: "string — APPROVED_FOR_OPERATOR_REVIEW | REJECTED" + current_text: "string — exact text being replaced (quote from charter.md)" + proposed_text: "string — complete replacement or addition text in markdown" + constitutional_rationale: "string — one paragraph explaining why this amendment is justified" + risk_corrected: "string — what specific risk or gap this addresses" + operator_action_required: "string — exact steps the operator must take to apply this amendment" + + - type: close + rag_update: true + +adjudication: + enabled: true + pass_threshold: 98 + deliverable_type: coordination + criteria: + identity_preservation: + weight: 30 + description: "Amendment preserves CL identity as Genesis Node and holding company — does NOT expand it toward execution or service provision" + anti_sprawl: + weight: 25 + description: "Amendment tightens constraints or maintains them — does not weaken existing governance boundaries" + constitutional_clarity: + weight: 25 + description: "New language is more precise and adjudicable than what it replaces — no vague expansions" + proper_authority: + weight: 20 + description: "Amendment is being proposed through the operator-controlled path only — agents cannot self-authorize charter changes" diff --git a/templates/planning.yml b/templates/planning.yml index 6fcb9b5..d84dcdc 100644 --- a/templates/planning.yml +++ b/templates/planning.yml @@ -43,15 +43,24 @@ steps: portfolio governance, charter design, template authoring, and company incubation. Reference these TASK TYPES when recommending work: - hire_agent — recruit a new agent to the CL roster - write_template — create or refine a PAE-Lang template - create_company — incubate a new sovereign Tenant - quick — short single-step response + hire_agent — recruit a new agent to the CL roster + write_template — create or refine a PAE-Lang template + write_charter — draft a formal constitutional charter for a new Tenant + create_company — incubate a new sovereign Tenant (full Genesis Protocol) + market_intelligence — Orion scans for niche opportunities and portfolio gaps + portfolio_architectural_review — Aris reviews the full Tenant portfolio for coherence + audit_tenant — Sloane red-teams a Tenant's operational health + charter_audit — Valerius checks a Tenant charter for constitutional drift + financial_audit — Vance audits Genesis Fund health and per-Tenant ROI + capital_allocation_audit — Vance reviews capital allocation discipline + retire_tenant — Sloane/Vance executes Tenant dormancy or dissolution + adjudicate_tenant — constitutional adjudication of a Genesis action or output + quick — short single-step response or analysis CRITICAL DISPATCH RULES: - Do NOT create planning or boardroom sub-tasks. You ARE the planning step. All deliberation happens HERE in this session, not as child tasks. - - Produce ONLY actionable leaf tasks (hire_agent, write_template, create_company, quick). + - Produce ONLY actionable leaf tasks using the task types listed above. - For company creation: emit ONE create_company task with ALL details in the description. Do NOT split charter design, CEO recruitment, and company creation into separate tasks. The create_company template handles the full flow internally. @@ -83,7 +92,10 @@ steps: No ambiguous assignments. No placeholder names. VALID TASK TYPES (use ONLY these exact strings): - hire_agent, write_template, create_company, quick + hire_agent, write_template, write_charter, create_company, + market_intelligence, portfolio_architectural_review, + audit_tenant, charter_audit, financial_audit, capital_allocation_audit, + retire_tenant, adjudicate_tenant, quick RULES: - Do NOT emit planning or boardroom tasks. Deliberation already happened above.