CodeAnvil Model Charter

Version: 1.0

Status: active foundation model

Date: 2026-07-21

System Thesis

CodeAnvil 将声明转化为受治理的运行状态。X-CodeAnvil 将未知可能性转化为受治理的 X。

CodeAnvil turns declarations into governed runtime state. X-CodeAnvil turns unknown possibilities into governed X.

Canonical Judgment

CodeAnvil, CodeAnvil Kernel, CKIMS, and X-CodeAnvil are not four peer products.

The stable model is:

1. CodeAnvil is the programmable infrastructure and execution system.

2. CodeAnvil Kernel is the deterministic execution kernel inside CodeAnvil.

3. CKIMS is the Human + Agent control plane for operating CodeAnvil.

4. X-CodeAnvil is the external X forge and operation system built on top of CodeAnvil.

5. In CKIMS, created systems are called `instances`; in world narrative and brand language, the created thing is called `X`.

Layer Order

Human / Codex / External Systems / Unknown Intent
        |
        v
X-CodeAnvil
        |
        v
CodeAnvil
        |
        +-- CKIMS
        +-- Platform Services
        +-- State, Event, Policy, Artifact, Release, Domain Ledgers
        |
        v
CodeAnvil Kernel
        |
        v
Cloudflare Application Ecosystem

Non-Negotiable Invariants

1. CodeAnvil can run without X-CodeAnvil.

2. X-CodeAnvil obtains digital runtime capability through CodeAnvil.

3. CodeAnvil Kernel is an internal deterministic kernel, not the public product name.

4. CKIMS is a control plane, not a public entity interface.

5. X-CodeAnvil must not bypass CodeAnvil to mutate Cloudflare resources.

6. Kernel must not own X business meaning, value judgment, or governance semantics.

7. Every state change has principal, plan, authorization, execution, verification, and evidence.

8. Cloudflare is the current runtime substrate, not the domain identity of CodeAnvil.

9. Codex is the current primary Agent Operator, not the only possible agent.

10. Conversation is never the final source of truth; it is compiled into model, plan, decision, ledger, or evidence.

11. CKIMS object vocabulary uses `instance`; public/world vocabulary uses `X`.

12. `x-codeanvil.io` is the X-CodeAnvil brand IO and must be governed as a CodeAnvil foundation domain asset.

Source Of Truth

The CodeAnvil Model document system is the upper document authority. CKIMS and Kernel ledgers are the runtime authority. Local Work files are temporary intake material only.

Naming And Terminology

Official Names

Boundary Rules

Required Object Vocabulary

Forbidden Naming Patterns

System Architecture

CodeAnvil

CodeAnvil accepts declarations, policies, artifacts, approvals, and operating commands. It returns governed runtime state, deployment evidence, resource state, audit history, and reconciliation signals.

Core planes:

CodeAnvil Kernel

Kernel standard loop:

Declare -> Validate -> Diff -> Plan -> Authorize -> Apply
   ^                                               |
   |                                               v
Reconcile <- Observe <- Record <- Verify <---------

Kernel is deliberately narrow. It receives authorized state changes, produces plans, applies provider operations through controlled drivers, verifies results, records evidence, and reconciles drift.

CKIMS

CKIMS exposes the same governed fact surface to Human and Agent operators:

CKIMS does not replace Cloudflare Dashboard. It defines which provider actions are allowed, why they are allowed, who approved them, what evidence exists, and how any future operator continues.

X-CodeAnvil

X-CodeAnvil turns unknown inputs into X Manifest and governed X:

Unknown -> Candidate X -> Specified X -> Forgeable X -> Commissioned X -> Operational X -> Evolved X

The digital runtime portion of X is compiled into CodeAnvil deployment specifications and becomes a CKIMS `instance` when approved. X meaning, business logic, governance, metrics, and evolution remain in X-CodeAnvil.

Contract Between X-CodeAnvil And CodeAnvil

Cloudflare Provider Model

Cloudflare is the current CodeAnvil runtime substrate. CodeAnvil should be Cloudflare-native first, while keeping its domain model independent from Cloudflare product names.

Provider Planes

Current CKIMS Interpretation

Binding Rule

When running inside Workers or Pages Functions, Cloudflare bindings are preferred over REST API calls for bound resources. REST API access remains a provider administration path used by local owner-deploy scripts and must be governed by provider contracts and LocalOnly secrets.

Provider Execution Policy

Provider-side create, change, delete, or route mutation requires:

1. Resource plan.

2. Owner approval.

3. Active provider execution policy.

4. Active runbook.

5. Rollback or compensation evidence.

6. Deployment ledger record.

7. Route smoke and inventory audit.

8. Audit log.

Security, Governance, And Audit

Principal Model

Human, Codex, autonomous agents, services, and X entities are principals. They operate through scoped workseats or service contracts.

Core Rules

Risk Scale

Evidence Chain

Intent
  -> Plan
  -> Approval
  -> Provider Execution Policy
  -> Runbook
  -> Deployment / Change Record
  -> Verification
  -> Audit
  -> Continuation State

Identity Mapping

Cloudflare Access identity must be mapped into CKIMS workseats through `identity_mappings`. Owner capability is never inferred from email alone unless the mapping is active and audited.

Formal identity, passkey, MFA, OIDC, and X instance SSO rules are defined by `08-IDENTITY-ACCESS-GOVERNANCE.md`.

Break-Glass

Emergency access must include:

Implementation Roadmap

Phase 0: Constitution

Deliver:

Exit condition: any Codex entering CodeAnvil can read the model, understand the hierarchy, and continue without guessing.

Phase 1: CodeAnvil Spine

Deliver:

Exit condition: a governed Cloudflare surface can be planned, approved, deployed, verified, audited, and rolled back.

Phase 2: Governed Operations

Deliver:

Exit condition: routine operations no longer depend on ad hoc Codex reasoning.

Phase 3: X Forge

Deliver:

Exit condition: X-CodeAnvil can define an X and ask CodeAnvil to produce its governed runtime.

Phase 4: X Operations

Deliver:

Exit condition: X operational meaning and CodeAnvil infrastructure facts are connected but not confused.

Phase 5: Evolution And Portfolio

Deliver:

Exit condition: multiple X entities can evolve while preserving model, evidence, and audit.

Domain And Surface Registry

Brand Domain

`x-codeanvil.io` is the planned X-CodeAnvil brand IO and the governed parent domain for public or semi-public CodeAnvil model surfaces.

This domain is a CodeAnvil foundation asset. Its subdomains are created through CKIMS resource plans and domain records, not ad hoc dashboard edits.

Planned Subdomains

X / Instance Rule

Public language uses X. CKIMS system language uses `instance`.

An X becomes operational only when CKIMS has an instance request, resource plan, security profile, allocation records, deployment evidence, and audit trail. Domains and subdomains are assigned by CKIMS to infrastructure or instances; no X receives ad hoc DNS or storage.

Actual Domain Rule

Actual domain count comes from CKIMS foundation assets with `asset_type=domain` only.

DNS records, Pages URLs, Worker default domains, Access application domains, aliases, routes, and deployment URLs are child records/evidence.

Creation Rule

No subdomain becomes official until it has:

1. Domain asset or parent domain record.

2. Resource plan.

3. Surface record.

4. Owner approval when public or production.

5. Deployment or route record.

6. Audit entry.

Document Library Governance

Principle

CodeAnvil is a growing architecture system. Its standards must be organized as document systems, not isolated notes.

The CodeAnvil Model document system is the upper authority. Specialized document systems extend it.

Current Document Systems

Required Library Classes

Registry Rule

Every document system must have:

1. Index JSON.

2. Charter.

3. Technical architecture document.

4. Security/governance document.

5. Runbook or execution model.

6. D1 `document_ledger` records.

7. D1 `persistent_ledger` source bundle.

8. CKIMS route or model endpoint when it must be machine-readable.

Extension Rule

Future CodeAnvil technical, architecture, deployment, and provider libraries should be added as sibling document systems under `BootstrapEntry`, then uploaded into CodeAnvil Kernel ledgers.

Identity And Access Governance

Position

CodeAnvil identity is a Kernel infrastructure concern. It is not owned by any single X instance, enterprise management system, website, or community system.

CKIMS owns the identity and access governance model for Human + Codex operation. X instances consume governed identity assertions and manage their own business roles under CKIMS policy.

Layers

Principal Vocabulary

Email address alone is never the identity authority. It is contact and recovery evidence unless mapped through active `identity_mappings` and CKIMS workseat policy.

Unified Identity Standard

The unified identity center is a CodeAnvil Kernel infrastructure standard. It should support:

CKIMS Access Model

CKIMS should be protected before broad public use by Cloudflare Access or an equivalent Zero Trust gate. Cloudflare Access authenticates the operator; CodeAnvil Kernel authorizes the operation through workseats, approvals, provider contracts, resource plans, and audit.

Codex access is not a free-floating role. Codex enters through the local bootstrap entry, reads Kernel context, and acts as a scoped operator under AIP and workseat rules.

X Instance SSO Model

Future enterprise, website, community, dashboard, portal, and VPN systems are X instances or instance types. They may accept OIDC SSO from the CodeAnvil identity center, but they do not own CKIMS identity policy.

An X instance may manage:

An X instance must not:

Email Relationship

CodeAnvil Email Management System supplies identity messages, not identity authority.

Zoho Mail provides governed human mailboxes such as `owner@x-codeanvil.io`.

ZeptoMail is planned as the transactional delivery provider for verification, recovery, MFA, security alert, admin notification, and future X instance transactional mail. It must not be activated for a sending domain until CKIMS has provider evidence, DNS plan, rollback evidence, Owner approval, deployment record, and verification audit.

Machine Rules

CodeAnvil Model Reconstitution And Local Boundary

Version: 1.0

Status: active reconstitution gate

Date: 2026-07-22

Purpose

This document corrects CodeAnvil from an expanding local context folder into a governed cloud operating model.

The local `CodeAnvil/` root is only an entry and temporary work surface. CKIMS is the durable system. The CodeAnvil Model is the upper authority. CKIMS ledgers, documents, operations, reports, work queue, approvals, and audit entries are the runtime authority.

Correct Layer Order

Codex / Human
  -> local CodeAnvil BootstrapEntry
  -> CodeAnvil Kernel
  -> CKIMS
  -> Cloudflare infrastructure ledgers and operating surfaces

`Work/` is not memory. `MemorySync/` is not permanent truth. `LocalOnly/` is credential custody only. Any durable item must be compiled into CKIMS.

Local Boundary Standard

Reconstitution Rule

The single CodeAnvil Model document system is the constitution of the system. New architecture, provider setup, domains, email identity, dashboards, AI assistants, work queues, and X instances must be registered against this model.

Codex must not rely on old conversation inference. On entry Codex reads:

1. `GET /entry`

2. `GET /panorama`

3. `GET /ckims/operating-system`

4. `GET /work-queue?status=active`

5. the target route named by the active work item

Memory Retirement Policy

Local `MemorySync/*.json` files are migration candidates. They may remain as mirrors while CKIMS is still being built, but they must not define the system.

Retirement sequence:

1. Inventory local memory mirrors.

2. Classify each mirror as credential-boundary, deploy evidence, operation evidence, obsolete diagnostic, or temporary task state.

3. Register active evidence in CKIMS D1 and object evidence in R2 where needed.

4. Replace repeated context files with work queue entries and operation logs.

5. Keep `MemorySync/current-agent-context.json` only as a thin local pointer until `/entry` and `/panorama` fully replace it.

6. Delete or archive retired mirrors only after CKIMS has accepted migration evidence.

CKIMS Required Planes

CKIMS must expose a Codex-operable overview before any enterprise or X instance is created:

Decision

CodeAnvil local remains small. CKIMS becomes the operating system. The CodeAnvil Model becomes the upper standard that both Human and Codex can read before performing work.

CKIMS Agent Assistant Readonly Plan

Version: 1.0

Status: active readonly planning gate

Date: 2026-07-22

Purpose

CKIMS needs a bounded assistant for routine infrastructure understanding, not an unbounded autonomous operator. The first assistant is read-only. It gathers CKIMS and Cloudflare posture, asks an approved Workers AI model to summarize and classify, then writes reports and suggested work items for Codex and Human review.

Cloudflare Capability Fit

Safety Boundary

The assistant may:

The assistant may not:

AI Model Selection Gate

Workers AI model selection must be data driven. Before testing any model, CKIMS records:

1. model identifier

2. model provider or organization

3. hosting/runtime provider

4. supported task type

5. pricing/cost metric

6. context limits or input constraints when available

7. data retention and privacy posture

8. jurisdiction and provider exclusion notes

9. CKIMS allowed use cases

10. CKIMS forbidden use cases

Privacy rule: do not select models from providers headquartered in China for private CKIMS infrastructure summaries, private logs, owner identity context, or provider configuration analysis.

Initial accepted task class is `infrastructure-summary-and-risk-classification`, not code execution and not provider mutation.

Report Contract

Each report writes:

First Test Sequence

1. Register the readonly plan.

2. Register model candidate fields and selection policy.

3. Read current Cloudflare Workers AI model catalog through official source or Cloudflare API.

4. Shortlist several non-China-hosted/provider-suitable models.

5. Register cost/security comparison in CKIMS.

6. Configure AI Gateway before test.

7. Run one synthetic report over redacted CKIMS sample data.

8. Human/Codex review output quality and cost.

Decision

CKIMS Agent Assistant v1 is a reporting and recommendation assistant. It is not an autonomous infrastructure mutator.

CKIMS Workers AI Model Candidate Registry

Version: 1.0

Status: active candidate registry

Date: 2026-07-22

Purpose

This registry records the first Workers AI model candidates for CKIMS Agent Assistant v1. It is a selection gate, not an inference deployment.

The goal is to find a safe, low-cost, non-China-provider model for readonly infrastructure summaries, governance-gap classification, and report drafting.

Official Evidence

Official Cloudflare sources used:

Selection Rules

Initial Candidate Classes

Excluded At This Gate

Models from DeepSeek, Zhipu/Z.ai, Qwen, Moonshot/Kimi, and BAAI are excluded from private CKIMS infrastructure-summary use at this gate because the current privacy rule excludes China-headquartered providers for private infrastructure analysis.

This is a CKIMS policy decision, not a judgment of model quality.

Deployment Lock

No AI inference is enabled by this registry. The next action is AI Gateway setup and a redacted synthetic report test.

CKIMS AI Gateway Synthetic Report Test

Version: 1.0

Status: active synthetic test gate

Date: 2026-07-22

Purpose

This gate verifies that CKIMS can use Cloudflare AI Gateway and Workers AI for a bounded, observable, low-risk report workflow.

This is not a production assistant deployment. It is a single synthetic test over redacted fake CKIMS evidence.

Gateway Policy

Gateway ID: `ckims-agent-assistant-v1`

Configuration target:

Test Model

Initial model: `@cf/ibm-granite/granite-4.0-h-micro`

Selection reason: low listed Workers AI cost and non-China-provider policy fit for infrastructure summaries.

Synthetic Input Only

The first prompt may include:

The first prompt must not include:

Expected Output

The model should produce concise JSON-like report content containing:

Acceptance

PASS means:

1. AI Gateway is listed or created.

2. The Workers AI request is routed through the gateway.

3. A model response is returned.

4. A sanitized report record is written to CKIMS.

5. No provider infrastructure mutation is performed beyond AI Gateway creation if missing.

Deployment Lock

After this test, CKIMS Agent Assistant remains readonly. Scheduled scans, Cron, Queues, Workflows, and R2 report objects require later gates.

CKIMS Readonly Collector Contract

Version: 1.0

Status: active contract gate

Date: 2026-07-22

Purpose

This document defines the first CKIMS readonly collector contract for the Agent Assistant.

The collector is the deterministic evidence layer. Workers AI may summarize only the evidence produced by this contract. The assistant must not independently discover secrets, mutate providers, deploy Workers, change DNS, send mail, approve actions, or expand scope.

Scope

Allowed first collector sources:

Forbidden first collector sources:

Redaction Rules

Every collector output must:

1. replace token-like strings with `[redacted-token-like-value]`

2. replace email local parts unless the address is an approved public role address

3. store raw evidence references separately from AI prompt content

4. include `synthetic_input_only` or `redacted_input_only`

5. include `mutation_performed: false`

Report Shape

Required report fields:

Execution Phases

Phase 1: contract only.

Phase 2: manual readonly collector dry run.

Phase 3: scheduled Cron collector.

Phase 4: Queue-backed evidence processing.

Phase 5: Workflow-backed review and approval loop.

Phase 6: low-risk auto-remediation proposals only. Provider mutation remains locked unless a separate execution gate is approved.

Acceptance

PASS means:

1. The collector contract is registered in CKIMS.

2. A redaction policy is active.

3. A manual readonly collector dry-run task is created.

4. No provider API read or write is executed by this contract gate.

5. AI inference remains limited to the previous synthetic test until the manual dry-run gate is implemented.

CKIMS Readonly Collector Manual Dry Run

Version: 1.0

Status: active execution gate

Date: 2026-07-22

Purpose

This gate runs the first manual CKIMS readonly collector dry run.

It validates that CKIMS can gather limited infrastructure metadata, redact it, pass only the redacted summary through Cloudflare AI Gateway and Workers AI, and write a human-reviewed report back to CKIMS.

Allowed Reads

This gate may read:

Forbidden Reads And Writes

This gate must not:

AI Prompt Boundary

Workers AI receives only a compact redacted evidence summary. Raw Cloudflare API bodies must not be sent to the model.

Acceptance

PASS means:

1. Cloudflare metadata reads succeed or fail with sanitized diagnostics.

2. CKIMS D1 counts are collected.

3. The AI report is generated through `ckims-agent-assistant-v1`.

4. The report is written to CKIMS.

5. The next gate is scheduled scan planning, not autonomous remediation.

CKIMS Agent Assistant Scheduled Scan Plan

Version: 1.0

Status: active planning gate

Date: 2026-07-22

Purpose

This document defines the first scheduled readonly scan plan for the CKIMS Agent Assistant.

The plan converts the manual readonly collector dry run into a governed automation design using Cloudflare Cron Triggers, Queues, Workflows, R2, D1, Workers AI, and AI Gateway.

This gate is a plan only. It must not enable Cron, create queues, deploy Workflows, write R2 report objects, mutate Cloudflare provider resources, send email, or auto-remediate infrastructure.

Runtime Composition

Recommended composition:

First Schedule

Recommended first schedule:

Report Storage

Use the existing CKIMS R2 bucket unless a later capacity or separation gate requires another bucket.

Recommended object prefixes:

Queue And Workflow Names

Planned Queue:

Planned Workflow:

Approval Rules

Owner approval is required before:

Acceptance

PASS means:

1. The scheduled scan plan is registered in CKIMS.

2. Planned resources are represented as resource plans.

3. Approval gates are registered.

4. The next task is a deployment readiness gate.

5. No Cloudflare provider resources are created or modified by this gate.

CKIMS Agent Assistant Scheduled Scan Deployment Readiness

Version: 1.0

Status: active readiness gate

Date: 2026-07-22

Purpose

This gate prepares CKIMS scheduled readonly scan automation for owner approval.

It does not create Cloudflare Queues, enable Cron Triggers, deploy Workflows, change Worker bindings, write R2 report objects, send notifications, or perform provider mutation.

Readiness Package

The readiness package contains five approval targets:

Deployment Order

After owner approval, deploy in this order:

1. Create Queue.

2. Add Worker Queue producer/consumer bindings.

3. Add scheduled handler and Cron Trigger.

4. Add Workflow binding and implementation.

5. Add R2 report write path.

6. Run manual scheduled simulation.

7. Enable daily schedule.

Rollback Rules

Rollback order:

1. Disable Cron Trigger.

2. Pause or remove Queue consumer.

3. Disable Workflow invocation path.

4. Lock R2 report write path.

5. Keep D1 audit and report metadata.

Acceptance

PASS means:

1. The readiness package is registered in CKIMS.

2. Approval ledger rows are created for each planned resource group.

3. The provider execution gate remains locked.

4. The next task is owner-approved provider execution.