Skip to content

Framework 1.3: carry method 2.0 into schemas and runtime - #3

Merged
oddtitoreal merged 2 commits into
mainfrom
revisione-metodo-2026-10
Oct 21, 2026
Merged

oddtitoreal merged 2 commits into
mainfrom
revisione-metodo-2026-10

Conversation

@oddtitoreal

Copy link
Copy Markdown
Owner

Framework 1.3.0: carries specula-method 2.0 into schemas and runtime. All schema additions are optional; existing artifacts stay valid.

What changes

  • New schemas: preferable_future (phase 4) and decision_log (phases 4 to 6), with modes, routing, persistence table, examples.
  • Optional fields: phase0_activation.framing; scenario archetype, closed_megatrends, open_variables, built_against_value, materialization_indicators; brand DNA operational_form, stress_test, documented_decisions, fragile_values, fallen_candidates, counterexamples; guardian drift_classification, expected_vs_observed, composite_alerts, escalation, action circle_deliberation.
  • scenario_type: "preferred" deprecated (removal planned for 2.0).
  • Fix: GUARDIAN_CRITICAL_LEVELS held "critical", a value phase6_guardian never accepts, so a rupture without re_speculate raised no alert. Now {"rupture"}; the Circle charter table is aligned with the schema enums.
  • Terminology 1.2, VERSIONS.md and ALIGNMENT.md cover all five repositories.

Tests

38 passed (30 before): new tests/test_method_v2_alignment.py, new examples in the schema contract test.

Open point

In the charter the External Auditor has no ordinary vote, yet majorities are expressed in fifths: with four voting members "4/5" cannot be computed. Thresholds not changed here.


Generated by Claude Code

Optional fields for framing, scenario construction rule, Value Stress
Test, drift classification and Decision Log review; new decision_log and
preferable_future schemas with modes, routing, persistence, examples and
tests. Fix GUARDIAN_CRITICAL_LEVELS, which held a value the schema never
accepted. Deprecate scenario_type "preferred". Align the Circle charter's
Guardian table with the schema; update terminology, VERSIONS, ALIGNMENT.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hqrE8mcDrvCiLz4UuT9nA
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-21T14:01:10.909944Z 5ff552d PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5ff552dbd8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/specula_agent/schemas.py Resolved
@oddtitoreal
oddtitoreal merged commit b26b58e into main Oct 21, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants