Configuration register
Section 21 of 22
This register records operating rules, starting defaults, and the measured costs or deployed identities required before use. Section 20 contains the starting values. Activation requires the evidence listed here.
| Configuration | Design or proposed default | Remaining binding before use |
|---|---|---|
| Initial domain | Safety. Rehearse typescript.precise.v1 against a frozen baseline. | Exact policy, schema, model, corpus, source revision, and supported operation identifiers. |
| Coverage | Full candidates require a scoped decision on the actual diff by U06. Targeted scope must follow a demonstrated mechanical rule. | Qualified council assignment, classification rules, mapped checks, and combined-change validation. |
| Production evaluation | Mandatory deterministic, live, adversarial, and integration evidence under a predeclared rule. | Measured cost, prescribed run list, case identifiers, repetition and acceptance criteria, and funded allowances. Rehearsal counts alone are insufficient. |
| Evidence | Authenticate actual execution for an exact candidate. | Runner image and key, evidence schema, provenance checks, retention, and provider-drift response. |
| Council operation | Two-of-three scoped agreement with defined abstention and failure handling. | Qualified instances, actual tool permissions, structured output, benchmark maintainer, fresh cases, and recurring requalification budget. |
| Founding challenges | Public authenticated factual and interpretive submissions. Contribution voting is unnecessary. | Working intake, qualification and appeal assignments, funded reproduction, and published access route. |
| Operating windows | Forty-eight hours for full releases and corpus changes, twenty-four for targeted releases. | Adoption after actual access and response testing. Count qualifying access only. |
| Coupled corpus changes | Separate notice for weakenings and one window at least as long as either applicable window. | Candidate-use versus activation records and exact coupled version references. |
| Challenge finality | Twenty-four hours per assignment, one replacement, and one ordinary appeal. | Assigned authorities, qualification appeal, timeout behavior, and urgent-protection exception. |
| Confidential cases | Committed inputs and expectations, sanitized public evidence, and a separately assigned examiner. | Access classification, examiner qualification and keys, reproducibility, disclosure deadline, and limits published before U11. |
| Production authority | Promotion-controller ownership with a scoped attested executor. Off-chain facts remain the executor's responsibility. | Implemented contract, target registry and chain, role and authority epoch, action schema, migration evidence, and actual executor drill. |
| Execution delay | One hour after U13 registration, with no founding prequeue overlap. | Adopted controller timing, expiry, cancellation, and replacement rules. |
| Emergency route | Immediate scoped containment and evaluated expedited restoration. | Guardian keys, exact allowed actions, mandatory emergency checks, any deferred work, and follow-up deadlines. |
| Confirmation | Confirm the intended external state before dependent action. | Chain-specific confirmation and reconciliation rule and explicit handling of unknown validity. |
| Work deadlines | Every funded quote has delivery and deploy/assess/cancel limits. | Category-specific times, alternate milestones, and accepted cancellation terms. |
| Holdback | Thirty days from observable use for substantial work, with full conditional fee. | Category adoption, required observation evidence, smaller-work schedules, and adjustment terms. |
| Repair and attribution | Duties and author exclusions remain separate from payment timing. | Causal standard, covered periods, post-payment consequences, self-disclosure treatment, and appeal. |
| Stakes and bonds | Disabled unless separately adopted. | Specific abuse or incentive purpose, funded collateral, forfeiture evidence, and correction route. |
| Bounties | Public intake can precede funded awards. Fixed promises require covered commitments. | Scope, priority, completion deadline, severity schedule, aggregate caps, reservation rule, and settlement deadline. |
| Review-fee share | A portion of earned review fees follows pool/burn routing after service costs. | Exact share, accounting base, collection timing, service reserve, and Epoche pricing authority. |
| Token tax | Retain 1% on covered buys and sells. Activation depends on tested routes. | Covered trades, collection, exemptions if adopted, supported integrations, and settlement tests including all costs. |
| Reward inventory target | Uncommitted EPOCHE units, with split-crossing and burning at equality when reserves are covered. | Token amount selected from the intended reward budget. No inferred dollar guarantee. |
| Protected reserves | Separate customer liabilities, accepted payments, remedies, operations, and emergency capacity from uncommitted token inventory. | Amounts by asset, funding source, accepted protection, and current accounting revision. |
| Reserve freshness | Maximum twenty-four hours, invalidated earlier by relevant changes. Stale or short coverage disables burning. | Accounting-worker authority, invalidation events, reconciliation, and actual covered assets. |
| Burn and conversion | Burn only designated inflows after the reserve check. Other-asset review fees require an authorized EPOCHE purchase if routed to token rewards or burning. | Destination, conversion limits, tax treatment, confirmation, and failed-transfer recovery. |
| Contributor settlement | Dollar quotes distinguish net realizable amounts from reference-priced token quantities. | Price source, conversion event, gross/net treatment, token and fee limits, usable route, and funded fallback. |
| Token service payments | Retain optional EPOCHE payment for dollar-quoted reviews. | Epoche's supported payment route, customer terms, service accounting, and integration tests. |
| Funding | No assumed 5,000 USDC founder deposit or hypothetical trading receipts. | Actual operating and reward assets from the adopted sources. |
| Automatic remedies | Coverage at rule adoption and new exposure, followed by entitlement-preserving execution. | Funded cap or exposure limit, intake reservation, remedy asset or service credit, and discretionary authority. |
| Governance influence | Record accepted work. Weighted voting remains disabled until its rules activate. | Credit allocation, valuation, snapshot, quorum, decay, delegation, thresholds, and corrections. |
| Founding control | Single controlling operator with automated routine roles and public challenge access. | Initial assignments, actual retained powers, disclosure, and a tested handover before claiming independent control. |
| Recovery | Founding recovery replaces failed workers while Bryan remains available. Broader resistance requires separately controlled recovery. | Replacement actors, notice, limits, lost-key evidence, and demonstrated independence for later claims. |
| Gas and job budgets | Rehearsal test-native amounts and operating estimate formula appear in section 20. | Actual funded wallets, estimated transaction set, fee ceiling, replenishment permission, time and cost limits. |
| Identity | Stable pseudonyms preserve work and entitlements. | Authentication, wallet rotation, lost-key evidence, limited private records, and optional later uniqueness rules. |
| Administration | Verify the actual tax, token-purchase/burn, service-payment, and contributor-payment arrangement. | Necessary payer or entity decisions, contribution licensing, payment eligibility, private retention, and reporting cadence. |
| Additional capabilities | Enable only with defined scope, qualified evidence, authority, funding, and recovery. | Separate activation decision for extra domains, independent governance, and optional incentives. |
Every active rule has a version, change authority, effective date, and treatment of existing work. An unbound production capability remains unavailable. Short rehearsal clocks, synthetic assets, or a provisional test key cannot activate it. Missing settings never mean unlimited spending, implicit approval, or permission to discard an existing claim.