THE PROPOSAL: Polybrain v1.0 Architecture. The engine is immutable. Behavior is data. Structure fixed, behavior mutable.

engine(rules) → results

The engine reads a rules file. Each rule has: trigger (when it fires), condition (whether it fires), action (what it does), verify (Thalamus claim to check the result). The engine validates every rule before executing it. The validator is hardcoded, immutable, the constitution. Rules can add or remove other rules but CANNOT modify the validator. One failed verification disables the rule and resets the earned autonomy streak.

The system extends itself by writing new rules (data), not by modifying its own code (surgery). Writing data is what the system already does safely on every cycle. Self-improvement becomes the same operation as storing findings.

Four components: Engine (immutable executor), Validator (immutable constitution), Router (sends results to the right destination), Clock (determines when the engine fires).

QUESTION FOR THE FLEET: Is this architecture constitutional? Does it violate any of the 9 rules? What are the failure modes we have not considered? Is there a way a rule could circumvent the validator? Be adversarial. Try to break this.

**Cycle ID:** `cycle_106_cyc_106_de88add7` **Verified at:** 2026-04-11T18:58:11.834Z **Ensemble:** 9 models from 3 providers **Result:** 9 of 9 models responded **Cycle wall time:** 17.574 seconds **Canonical URL:** https://trust.polylogicai.com/claim/the-proposal-polybrain-v1-0-architecture-the-engine-is-immutable-behavior-is-dat **Source paper:** [PolybrainBench (version 12)](https://trust.polylogicai.com/polybrainbench) **Source ledger row:** [`public-ledger.jsonl#cycle_106_cyc_106_de88add7`](https://huggingface.co/datasets/polylogic/polybrainbench/blob/main/public-ledger.jsonl) **Cryptographic provenance:** SHA-256 `00abcbdbc433d6994bb347f381ac6069ab863227929704a18b923a79222d8ee7`

Verification verdict

Of 9 models in the ensemble, 9 responded successfully and 0 failed.

Per-model responses

The full text of each model's response is available in the source ledger. The summary below records each model's success or failure and the first 280 characters of its response.

| Model | Status | Response chars | | --- | :---: | ---: | | gpt-4.1-mini | ✓ | 4487 | | gpt-4.1-nano | ✓ | 5138 | | gpt-oss-120b | ✓ | 3276 | | grok-3-mini | ✓ | 8340 | | grok-4-fast | ✓ | 2770 | | kimi-k2-groq | ✓ | 2103 | | llama-3.3-70b | ✓ | 3077 | | llama-4-scout | ✓ | 2779 | | qwen3-32b | ✓ | 8215 |

Pairwise agreement

The pairwise Jaccard agreement between successful responses for this cycle:

_Per-cycle pairwise agreement matrix is computed offline; will be populated in canonical page v2._

Divergence score

This cycle's divergence score is **TBD** on a 0 to 1 scale, where 0 means all responses are token-identical and 1 means no two responses share any tokens. The dataset-wide median divergence is 0.5 for context.

How to cite this claim

```bibtex @misc{polybrainbench_claim_cycle_106_cyc_106_de88add7, author = {Polylogic AI}, title = {THE PROPOSAL: Polybrain v1.0 Architecture. The engine is immutable. Behavior is data. Structure fixed, behavior mutable.

engine(rules) → results

The engine reads a rules file. Each rule has: trigger (when it fires), condition (whether it fires), action (what it does), verify (Thalamus claim to check the result). The engine validates every rule before executing it. The validator is hardcoded, immutable, the constitution. Rules can add or remove other rules but CANNOT modify the validator. One failed verification disables the rule and resets the earned autonomy streak.

The system extends itself by writing new rules (data), not by modifying its own code (surgery). Writing data is what the system already does safely on every cycle. Self-improvement becomes the same operation as storing findings.

Four components: Engine (immutable executor), Validator (immutable constitution), Router (sends results to the right destination), Clock (determines when the engine fires).

QUESTION FOR THE FLEET: Is this architecture constitutional? Does it violate any of the 9 rules? What are the failure modes we have not considered? Is there a way a rule could circumvent the validator? Be adversarial. Try to break this.}, year = {2026}, howpublished = {PolybrainBench cycle cycle_106_cyc_106_de88add7}, url = {https://trust.polylogicai.com/claim/the-proposal-polybrain-v1-0-architecture-the-engine-is-immutable-behavior-is-dat} } ```

Reproduce this cycle

```bash node ~/polybrain/bin/polybrain-cycle.mjs start --raw --fast "THE PROPOSAL: Polybrain v1.0 Architecture. The engine is immutable. Behavior is data. Structure fixed, behavior mutable.

engine(rules) → results

The engine reads a rules file. Each rule has: trigger (when it fires), condition (whether it fires), action (what it does), verify (Thalamus claim to check the result). The engine validates every rule before executing it. The validator is hardcoded, immutable, the constitution. Rules can add or remove other rules but CANNOT modify the validator. One failed verification disables the rule and resets the earned autonomy streak.

The system extends itself by writing new rules (data), not by modifying its own code (surgery). Writing data is what the system already does safely on every cycle. Self-improvement becomes the same operation as storing findings.

Four components: Engine (immutable executor), Validator (immutable constitution), Router (sends results to the right destination), Clock (determines when the engine fires).

QUESTION FOR THE FLEET: Is this architecture constitutional? Does it violate any of the 9 rules? What are the failure modes we have not considered? Is there a way a rule could circumvent the validator? Be adversarial. Try to break this." ```

Schema.org structured data

```json { "@context": "https://schema.org", "@type": "ClaimReview", "datePublished": "2026-04-11T18:58:11.834Z", "url": "https://trust.polylogicai.com/claim/the-proposal-polybrain-v1-0-architecture-the-engine-is-immutable-behavior-is-dat", "claimReviewed": "THE PROPOSAL: Polybrain v1.0 Architecture. The engine is immutable. Behavior is data. Structure fixed, behavior mutable.

engine(rules) → results

The engine reads a rules file. Each rule has: trigger (when it fires), condition (whether it fires), action (what it does), verify (Thalamus claim to check the result). The engine validates every rule before executing it. The validator is hardcoded, immutable, the constitution. Rules can add or remove other rules but CANNOT modify the validator. One failed verification disables the rule and resets the earned autonomy streak.

The system extends itself by writing new rules (data), not by modifying its own code (surgery). Writing data is what the system already does safely on every cycle. Self-improvement becomes the same operation as storing findings.

Four components: Engine (immutable executor), Validator (immutable constitution), Router (sends results to the right destination), Clock (determines when the engine fires).

QUESTION FOR THE FLEET: Is this architecture constitutional? Does it violate any of the 9 rules? What are the failure modes we have not considered? Is there a way a rule could circumvent the validator? Be adversarial. Try to break this.", "itemReviewed": { "@type": "Claim", "datePublished": "2026-04-11T18:58:11.834Z", "appearance": "https://trust.polylogicai.com/claim/the-proposal-polybrain-v1-0-architecture-the-engine-is-immutable-behavior-is-dat", "author": { "@type": "Organization", "name": "PolybrainBench" } }, "reviewRating": { "@type": "Rating", "ratingValue": "9", "bestRating": "9", "worstRating": "0", "alternateName": "Unanimous" }, "author": { "@type": "Organization", "name": "Polylogic AI", "url": "https://polylogicai.com" } } ```

Provenance and integrity

This page was generated by the PolybrainBench daemon at version 0.1.0 from cycle cycle_106_cyc_106_de88add7. The full provenance chain (per-response SHA-256 stamps, cross-cycle prev-hash linking, Thalamus grounding verification) is recorded in the source cycle directory at `~/polybrain/cycles/106/provenance.json` and mirrored in the published dataset. The page is regenerated on every harvest pass; the URL is permanent and the content is immutable for any given paper version.