From 489923e9f9f7aa84973b3c1bad4f1bcf2afa32cd Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:12:39 +0100 Subject: [PATCH 1/7] docs: record bounded Continuity publication plan --- .../plans/continuity-public-introduction.json | 41 +++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 docs/plans/continuity-public-introduction.json diff --git a/docs/plans/continuity-public-introduction.json b/docs/plans/continuity-public-introduction.json new file mode 100644 index 0000000..36e3a71 --- /dev/null +++ b/docs/plans/continuity-public-introduction.json @@ -0,0 +1,41 @@ +{ + "task_id": "282f117f-e976-4ca2-871a-242a41a1526b", + "steps": [ + { + "file_path": "LEGACY_FOUNDRY.md", + "action": "create", + "rationale": "Preserve the complete pre-rebrand README byte-for-byte at repository root so its relative links remain valid. Source commit: 2639b8ebeeb485950a8faed17491b03ff440b354; source blob: 7caeb132210e40d8f98ed587204eef41cb03d2dd.", + "dependencies": [] + }, + { + "file_path": "README.md", + "action": "modify", + "rationale": "Introduce Continuity publicly through the original engineering problem, architecture, evidence, limitations, and historical origin. Distinguish merged code from the unmerged evidence-retention PR #6.", + "dependencies": ["LEGACY_FOUNDRY.md"] + }, + { + "file_path": "CLAUDE.md", + "action": "modify", + "rationale": "Add the public-name and compatibility boundary without changing the existing technical guidance or historical rules.", + "dependencies": ["README.md"] + }, + { + "file_path": "docs/publication.md", + "action": "create", + "rationale": "Record the approved repository name, description, topics, draft announcement, evidence boundaries, and outstanding owner-admin and licence decisions.", + "dependencies": ["README.md"] + } + ], + "risks": [ + "The available GitHub connector cannot change repository name, description, or topics; do not report those admin actions as completed.", + "Do not merge PR #6 or this documentation PR without separate approval.", + "Do not advertise pending branch functionality as merged or imply that passing deterministic tests proves live autonomous operation.", + "Preserve existing licensing terms; public-facing documentation is not authorization to grant an open-source licence.", + "Keep foundry imports, package metadata, runtime code, workflow names, and historical commits unchanged." + ], + "open_questions": [ + "Repository owner must apply the GitHub Settings and About changes.", + "Repository owner must decide licensing before describing the project as open source or inviting external reuse." + ], + "estimated_complexity": "small" +} From 9c88d3b66592d32c2bc0e7eb09852f050a123773 Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:15:35 +0100 Subject: [PATCH 2/7] docs: introduce Continuity as the public identity of UCF Lead with the original continuity problem, distinguish merged evidence from open PR #6, preserve the prior README verbatim, and document the remaining owner-admin and licence decisions. No runtime, package, workflow, or historical commit changes. --- CLAUDE.md | 14 +- LEGACY_FOUNDRY.md | 432 +++++++++++++++++++++++++++++++++++++++++ README.md | 457 ++++++++------------------------------------ docs/publication.md | 101 ++++++++++ 4 files changed, 630 insertions(+), 374 deletions(-) create mode 100644 LEGACY_FOUNDRY.md create mode 100644 docs/publication.md diff --git a/CLAUDE.md b/CLAUDE.md index d75ff7b..c2fbaa8 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -1,4 +1,16 @@ -# UCF — Project Guidance +# Continuity — Project Guidance + +## Naming and publication + +**Continuity** is the public-facing name of the experiment previously documented as **UCF / Unicorn Foundry**. Use Continuity in new public introductions. Preserve UCF and Unicorn Foundry when describing the history or referring to existing technical names. + +This is a documentation rebrand, not a package or runtime migration. Keep `foundry` imports, the `unicorn-foundry` distribution name, `FOUNDRY_*` configuration, workflow identifiers, historical documents, and existing technical contracts unchanged unless a separate task explicitly migrates them. + +The original README is preserved verbatim in `LEGACY_FOUNDRY.md`. The public description, topics, draft announcement, and remaining launch decisions live in `docs/publication.md`. A documentation commit does not change GitHub repository settings or grant an open-source licence. + +Distinguish merged capabilities from unmerged PR work in every public claim. At this rebrand's preparation, PR #6 remains open and unmerged. Do not merge it or this documentation PR as part of the naming pass. + +The implementation guidance below retains its UCF/Foundry terminology; the discontinued Unicorn product is historical context, not a reason to revive it. ## What This Repo Is diff --git a/LEGACY_FOUNDRY.md b/LEGACY_FOUNDRY.md new file mode 100644 index 0000000..7caeb13 --- /dev/null +++ b/LEGACY_FOUNDRY.md @@ -0,0 +1,432 @@ +# UCF + +**An experiment in persistent machine operation across changing state.** + +UCF began as Unicorn Foundry, the execution side of a discontinued project called Unicorn. Unicorn explored how a changing environment could be made machine-legible through **signals → evidence → state → legibility**. UCF explored the complementary problem: once a machine has a representation of its current environment, how can it change that environment deliberately, determine what actually happened, and continue from the resulting state? + +The original implementation was built around Claude and software-engineering workflows. The underlying systems question was broader: + +> **What must exist around an intelligent model for it to remain coherent while the environment it operates in changes?** + +UCF treats the model as a participant in the system, not the system itself. + +## The Loop + +```text +WORLD + │ + ▼ +OBSERVATION + │ + ▼ +EVIDENCE + │ + ▼ +STATE(t) + │ + ▼ +REASON / DECIDE + │ + ▼ +INTENT + │ + ▼ +PLAN + │ + ▼ +CONTROLLED EXECUTION + │ + ▼ +VERIFICATION / REVIEW + │ + ▼ +OUTCOME + │ + ▼ +STATE(t+1) + └──────────────↻ +``` + +The important object is the **state transition**. + +A model may reason, plan, classify, review, or propose an action. UCF surrounds those capabilities with explicit state, typed transitions, isolated execution, deterministic verification, independent evaluation, durable artifacts, and event history. + +That distinction can be summarized as: + +**intelligence at an instant ≠ intelligence through time** + +## Origin + +UCF was originally implemented as **Unicorn Foundry**, an internal control plane for Unicorn Protocol. + +The two projects explored opposite sides of one loop: + +```text +Unicorn +signals → evidence → state → legibility + +UCF / Unicorn Foundry +state → intent → plan → action → verification → transition +``` + +Together, the intended system was: + +```text +world + ↓ +representation + ↓ +intelligence + ↓ +controlled action + ↓ +world' + ↓ +representation' + ↻ +``` + +Unicorn is no longer an active project. UCF is being preserved and generalized because the infrastructure problem it exposed is not specific to Unicorn. + +This repository does **not** claim to implement a learned world model or a complete architecture for general intelligence. It is a software-systems experiment in maintaining coherent machine operation across observation, action, consequence, and time. + +## What The Existing Implementation Actually Contains + +The historical Foundry implementation already provides concrete machinery for this experiment: + +- a typed run-state machine; +- isolated git worktrees for actions; +- structured planning artifacts; +- model/provider routing; +- deterministic build, test, lint, and schema verification; +- independent diff review; +- persistent run events and artifacts; +- PostgreSQL-backed run state; +- Redis-backed work queues; +- evidence and extraction contracts; +- evaluation infrastructure; +- deterministic hooks for policy enforcement; +- retry, cancellation, and failure states. + +Some originally planned paths remain incomplete. In particular, parts of the extraction/batch pipeline are still Phase 1 stubs. The repository should therefore be read as a working experimental system with unfinished surfaces, not as a completed general architecture. + +## Historical Implementation + +The codebase still uses its original **Foundry** terminology and contains Unicorn-specific adapters, schemas, task types, and documentation. Those are retained for now because they are evidence of how the experiment emerged. + +The current restructuring deliberately starts with the **conceptual boundary** before rewriting the runtime: + +```text +historical implementation generalized interpretation + +Unicorn state → environment state +Unicorn canon → state/evidence contracts +Claude → intelligence provider +Foundry run → controlled state transition +git worktree → isolated action environment +verification → transition validation +review → independent evaluation +run artifacts → durable transition evidence +PR → one possible action outcome +``` + +The long-term architecture should not require Claude, GitHub, source code, or Unicorn. Those are properties of the first implementation, not invariants of UCF. + +## Architectural Invariants + +1. **State is explicit.** The system should not depend on a model reconstructing its entire operating reality from a prompt. +2. **Actions produce transitions.** Work is understood as movement from a known state to a resulting state. +3. **Evidence survives inference.** Claims about what happened should remain traceable to observations and artifacts. +4. **Execution is controlled.** Intelligence proposes or performs actions inside explicit boundaries. +5. **Verification is separate from generation.** Producing an action and establishing that it worked are different operations. +6. **History is durable.** Meaningful transitions leave events and artifacts behind. +7. **Models are replaceable participants.** UCF should not depend conceptually on one provider, model family, or reasoning architecture. +8. **Continuity is a systems property.** Long-horizon coherence comes from the loop around intelligence as well as from intelligence itself. + +## Current Direction + +This repository is being reopened as UCF rather than maintained as an active Unicorn Foundry product. + +A provider-neutral UCF foundation now lives alongside the historical Foundry runtime: + +- `IntelligenceProvider` separates orchestration from a concrete model vendor; +- `ExecutionEnvironment` separates isolated execution from Git worktrees; +- provider-neutral transition contracts represent state, evidence, actions, observations, verification, and outcomes; +- `TransitionEngine` closes a state → action → observation → verification → outcome loop; +- `TransitionJournal` requires the verified outcome to survive the call; +- `FoundryTransitionRuntime` maps the historical planner, implementer, verifier, migration guard, worktree manager, and artifact store onto those interfaces; +- integration tests exercise that adapter with a real Git repository and real worktree isolation. + +The abstraction is therefore exercised by the original machinery, not only by fakes. The remaining P0 boundary is **runtime convergence**: the backwards-compatible `RunEngine` still owns the old database/event/PR lifecycle and must delegate its core transition work to the UCF path. PR creation should become publication after an accepted transition rather than the definition of completion. + +See [RETROSPECTIVE.md](RETROSPECTIVE.md) for the present-day interpretation, [docs/runtime-decoupling-audit.md](docs/runtime-decoupling-audit.md) for the migration map, and [docs/architecture.md](docs/architecture.md) for the original Foundry architecture specification. + +## Repository Map + +```text +UCf/ +├── README.md # current UCF thesis and status +├── RETROSPECTIVE.md # historical interpretation boundary +├── CLAUDE.md # guidance for future agents/engineering +├── docs/ +│ ├── ucf-architecture.md # generalized architecture mapping +│ ├── runtime-decoupling-audit.md # migration map and remaining coupling +│ └── architecture.md # original Unicorn Foundry specification +├── foundry/ +│ ├── contracts/ +│ │ ├── transition_models.py # state, evidence, action, outcome contracts +│ │ └── ... # historical Foundry contracts +│ ├── runtime/ +│ │ ├── interfaces.py # observer/planner/executor/verifier/journal +│ │ └── transition_engine.py # provider-neutral state-transition loop +│ ├── adapters/ +│ │ └── foundry_transition.py # historical Foundry -> UCF capability bridge +│ ├── environments/ +│ │ ├── base.py # ExecutionEnvironment contract +│ │ ├── git_worktree.py # concrete execution environment adapter +│ │ └── git_observer.py # explicit before/after Git state +│ ├── providers/ +│ │ ├── base.py # IntelligenceProvider contract +│ │ └── claude_*.py # historical/default Claude adapters +│ ├── orchestration/ # historical Foundry run machinery +│ ├── verification/ # historical deterministic code verification +│ ├── git/ # historical Git/PR action surface +│ ├── tasks/ # historical Foundry task implementations +│ ├── db/ # historical run persistence +│ └── storage/ +│ └── transition_journal.py # durable UCF outcome adapter +├── app/ # historical FastAPI control plane +├── workers/ # historical background workers +├── canon/ # historical Unicorn domain contracts +├── hooks/ # historical deterministic safeguards +├── tests/ +│ └── unit/runtime/ # provider-neutral transition-loop tests +└── .github/workflows/ + └── ucf-foundation.yml # compile, lint, foundation + regression tests +``` + +The repository intentionally contains both the generalized UCF foundation and the historical Foundry implementation. The historical directories are not being renamed away until their behavior has been migrated through exercised UCF interfaces. + +## Historical Foundry Runtime + +The sections below document the original concrete runtime. They are retained because they show how the systems problem was first implemented; they should not be read as requirements of the generalized UCF architecture. + +## Historical Foundry Task Types + + +| Task Type | Description | Model Routing | +|-----------|-------------|---------------| +| `endpoint_build` | Build new API endpoints in unicorn-app | Sonnet (plan/impl), Opus (review) | +| `feature_slice` | Implement feature slices across the stack | Sonnet (plan/impl), Opus (review) | +| `bug_fix` | Diagnose and fix bugs with regression tests | Sonnet (plan/impl), Opus (review) | +| `refactor` | Refactor code with safety verification | Sonnet (plan/impl), Opus (review) | +| `migration_plan` | Database migration planning and execution | Opus (plan/review/guard) | +| `architecture_review` | Architecture-level review and analysis | Opus (plan/review) | +| `review_diff` | Standalone independent diff review | Opus (review) | +| `extraction_batch` | Batch signal-to-event extraction | Sonnet (extract), Haiku (classify) | +| `evidence_classification` | Classify evidence strength levels | Haiku (classify) | +| `eval_run` | Run evaluation suites against model outputs | Sonnet (evaluate) | +| `canon_update` | Update shared schemas and domain docs | Opus (plan/review), Sonnet (impl) | + +## Historical Foundry Run Lifecycle + +``` +queued → creating_worktree → planning → implementing → verifying + → verification_passed → reviewing → pr_opened → completed +``` + +Failure states: `plan_failed`, `verification_failed`, `review_failed`, `cancelled`, `errored` + +Failed runs in `plan_failed`, `verification_failed`, or `review_failed` can be retried (transitions back to `queued`). Any non-terminal run can be cancelled. + +## Historical Foundry API Endpoints + +| Method | Path | Description | +|--------|------|-------------| +| `GET` | `/v1/health` | Health check | +| `POST` | `/v1/runs` | Submit a new task run | +| `GET` | `/v1/runs/{id}` | Get run status and metadata | +| `GET` | `/v1/runs/{id}/events` | Get run events (state transitions) | +| `GET` | `/v1/runs/{id}/artifacts` | List run artifacts | +| `POST` | `/v1/runs/{id}/cancel` | Cancel an in-progress run | +| `POST` | `/v1/runs/{id}/retry` | Retry a failed run | +| `POST` | `/v1/reviews` | Request an independent review | +| `POST` | `/v1/specs/plan` | Generate a plan from a spec | +| `POST` | `/v1/patches/apply` | Apply a patch to a worktree | +| `POST` | `/v1/batches/extract` | Start a batch extraction job | +| `GET` | `/v1/batches/{id}` | Get batch status | +| `GET` | `/v1/batches/{id}/results` | Get extraction results | +| `POST` | `/v1/evals/run` | Run an evaluation suite | +| `GET` | `/v1/evals/{id}` | Get eval results | +| `POST` | `/v1/worktrees/cleanup` | Clean up stale worktrees | + +## Historical Foundry Subagents + +| Agent | Role | Model | +|-------|------|-------| +| **Planner** | Produces structured `PlanArtifact` with file-level steps | Sonnet / Opus | +| **Backend Implementer** | Executes plans in Go (unicorn-app API) | Sonnet | +| **Frontend Implementer** | Executes plans in TypeScript (Next.js) | Sonnet | +| **Reviewer** | Independent diff review (never sees the plan) | Opus | +| **Extractor** | Signal-to-event structured extraction | Sonnet | +| **Migration Guard** | High-scrutiny review for migrations/auth/infra | Opus | +| **Repo Explorer** | Read-only codebase reconnaissance | Haiku | + +## Historical Foundry Claude Code Skills + +| Skill | Description | +|-------|-------------| +| `spec-to-plan` | Generate a structured implementation plan from a spec | +| `endpoint-generator` | Scaffold a new API endpoint end-to-end | +| `safe-refactor` | Refactor code with automatic verification | +| `review-diff` | Review any diff independently | +| `issue-to-pr` | Resolve a GitHub issue from triage to PR | +| `extract-signals` | Run signal extraction pipeline | +| `run-eval` | Execute evaluation suites | + +## Historical Foundry Hooks (Deterministic Enforcement) + +| Hook | Trigger | Purpose | +|------|---------|---------| +| `block_secrets.sh` | Pre: Read, Edit, Write | Block access to `.env`, `*.key`, `*secrets*`, etc. | +| `block_protected_paths.sh` | Pre: Edit, Write | Guard `migrations/`, `auth/`, `infra/`, Docker files | +| `require_plan.sh` | Pre: Edit, Write | Block edits without a stored plan | +| `verify_after_edit.sh` | Post: Edit, Write | Run verification after file modifications | +| `log_tool_call.sh` | Post: all tools | Log every tool invocation for auditability | + +## Historical Foundry MCP Profiles + +Runs can be scoped to specific MCP server access: + +| Profile | Servers | Use Case | +|---------|---------|----------| +| `none` | — | Default, no external access | +| `github_only` | GitHub | Code builds, PR workflows | +| `github_postgres_readonly` | GitHub + Postgres (read-only) | Research with data access | +| `research_full` | GitHub + Postgres (read-only) | Full research capabilities | +| `app_build_minimal` | GitHub | Minimal build access | + +## Historical Foundry Model Routing + +| Model | Use Case | +|-------|----------| +| **Opus 4.6** | Architecture, critical planning, review, migration guard, red-teaming | +| **Sonnet 4.6** | Implementation, structured extraction, endpoint building, evals | +| **Haiku 4.5** | Classification, tagging, reconnaissance, simple preprocessing | + +Routing is defined in `foundry/orchestration/model_router.py`. Override via `model_override` in task requests when justified. + +## Historical Foundry Database Schema + +PostgreSQL tables managed via Alembic: + +| Table | Purpose | +|-------|---------| +| `runs` | Run lifecycle records (state, branch, PR URL, metadata) | +| `run_events` | State transition events with timing and token usage | +| `run_artifacts` | Artifact metadata (type, storage path, checksum) | +| `worktrees` | Git worktree tracking and cleanup state | +| `batch_jobs` | Batch extraction/processing jobs | +| `batch_items` | Individual items within batch jobs | +| `eval_runs` | Evaluation run records with metrics | +| `verification_results` | Deterministic verification step results | + +## Prerequisites + +- Python 3.12+ +- Docker and Docker Compose +- Git + +## Setup + +```bash +# Start Postgres and Redis +docker compose up -d postgres redis + +# Install dependencies +pip install -e ".[dev]" + +# Run database migrations +alembic upgrade head + +# Run the API server +uvicorn app.main:app --host 0.0.0.0 --port 8000 +``` + +Or run everything via Docker: + +```bash +export ANTHROPIC_API_KEY= +export GITHUB_TOKEN= +docker compose up +``` + +This starts the API server, run worker, and batch worker with shared Postgres and Redis. + +The API is available at `http://localhost:8000`. Health check: `GET /v1/health`. + +## Configuration + +All settings use the `FOUNDRY_` env prefix (via pydantic-settings): + +| Variable | Default | Description | +|----------|---------|-------------| +| `FOUNDRY_DATABASE_URL` | `postgresql+asyncpg://foundry:foundry@localhost:5432/foundry` | PostgreSQL connection | +| `FOUNDRY_REDIS_URL` | `redis://localhost:6379` | Redis connection | +| `FOUNDRY_ANTHROPIC_API_KEY` | — | Anthropic API key | +| `FOUNDRY_GITHUB_TOKEN` | — | GitHub token for PR operations | +| `FOUNDRY_MAX_CONCURRENT_RUNS` | `5` | Max parallel run executions | +| `FOUNDRY_MAX_RETRIES_PER_RUN` | `3` | Max retry attempts per run | +| `FOUNDRY_WORKTREE_BASE_PATH` | `/tmp/foundry-worktrees` | Worktree storage directory | +| `FOUNDRY_LOG_LEVEL` | `INFO` | Log verbosity | + +## Development + +```bash +# Run tests +pytest + +# Lint and type check +ruff check . +mypy . + +# Run a task via CLI +python scripts/run_task.py --type endpoint_build --spec "Add GET /v1/companies/{id}/timeline" + +# Seed the database with test data +python scripts/seed_db.py + +# Export artifacts for inspection +python scripts/export_artifacts.py --run-id +``` + +## Tech Stack + +| Component | Technology | +|-----------|-----------| +| API Framework | FastAPI 0.115+ | +| Data Validation | Pydantic 2.9+ | +| Database ORM | SQLAlchemy 2.0+ (async) | +| Database Driver | asyncpg | +| Migrations | Alembic | +| Task Queue | Redis 5.2+ | +| AI Provider | Anthropic SDK 0.40+ (Agent SDK, Messages API, Batch API) | +| HTTP Client | httpx | +| Object Storage | boto3 (S3-compatible) | +| Logging | python-json-logger | +| Build System | hatchling | +| Linting | ruff | +| Type Checking | mypy (strict mode) | +| Testing | pytest + pytest-asyncio | + +## Historical Foundry Language Boundaries + +- **Python** — this repo (Foundry). All orchestration, extraction, eval code. +- **Go** — unicorn-app backend. Foundry writes Go code into unicorn-app via PRs. +- **TypeScript** — unicorn-app frontend. Foundry writes TS code into unicorn-app via PRs. + +Foundry never mixes languages. The appropriate implementer subagent is selected based on the target. + +## License + +Internal use only. Not licensed for external distribution. diff --git a/README.md b/README.md index 7caeb13..ba6e692 100644 --- a/README.md +++ b/README.md @@ -1,432 +1,143 @@ -# UCF +# Continuity -**An experiment in persistent machine operation across changing state.** +**An experiment in intelligence through time.** -UCF began as Unicorn Foundry, the execution side of a discontinued project called Unicorn. Unicorn explored how a changing environment could be made machine-legible through **signals → evidence → state → legibility**. UCF explored the complementary problem: once a machine has a representation of its current environment, how can it change that environment deliberately, determine what actually happened, and continue from the resulting state? +A useful model response is not the same thing as a coherent sequence of actions. -The original implementation was built around Claude and software-engineering workflows. The underlying systems question was broader: +A system can produce a good plan and lose the reason for it. It can make a change without establishing what actually changed. It can finish a task and leave the next operation with no reliable account of the result. -> **What must exist around an intelligent model for it to remain coherent while the environment it operates in changes?** - -UCF treats the model as a participant in the system, not the system itself. - -## The Loop - -```text -WORLD - │ - ▼ -OBSERVATION - │ - ▼ -EVIDENCE - │ - ▼ -STATE(t) - │ - ▼ -REASON / DECIDE - │ - ▼ -INTENT - │ - ▼ -PLAN - │ - ▼ -CONTROLLED EXECUTION - │ - ▼ -VERIFICATION / REVIEW - │ - ▼ -OUTCOME - │ - ▼ -STATE(t+1) - └──────────────↻ -``` +Continuity explores the infrastructure around that problem: explicit state, controlled action, observation, verification, and a record that survives the interaction. -The important object is the **state transition**. +> **The model is a participant in the loop, not the loop itself.** -A model may reason, plan, classify, review, or propose an action. UCF surrounds those capabilities with explicit state, typed transitions, isolated execution, deterministic verification, independent evaluation, durable artifacts, and event history. +This is an experimental software runtime, originally developed as **Unicorn Foundry / UCF**. “Intelligence through time” names the question being investigated, not a claim that the repository has solved it. -That distinction can be summarized as: +[Architecture](#architecture) · [Evidence and status](#evidence-and-status) · [Run the tests](#run-the-tests) · [Origin](#origin) · [Retrospective](RETROSPECTIVE.md) -**intelligence at an instant ≠ intelligence through time** +## The problem -## Origin +A model call starts with context and produces an output. An operating system around that call has additional responsibilities: representing its environment, tracking what is known, deciding which actions are permitted, checking consequences, and carrying useful state forward. -UCF was originally implemented as **Unicorn Foundry**, an internal control plane for Unicorn Protocol. +Continuity treats these as explicit engineering concerns rather than assuming they disappear when the model improves. -The two projects explored opposite sides of one loop: +The working question is: -```text -Unicorn -signals → evidence → state → legibility - -UCF / Unicorn Foundry -state → intent → plan → action → verification → transition -``` +> **What must exist around an intelligent model for it to remain coherent while the environment it operates in changes?** -Together, the intended system was: +## The loop ```text -world - ↓ -representation - ↓ -intelligence - ↓ -controlled action - ↓ -world' - ↓ -representation' - ↻ +environment + ↓ observe +state(t) + evidence + ↓ reason / plan +proposed action + ↓ controlled execution +changed environment + ↓ observe and verify +outcome + observed state(t+1) + ↺ next operation ``` -Unicorn is no longer an active project. UCF is being preserved and generalized because the infrastructure problem it exposed is not specific to Unicorn. - -This repository does **not** claim to implement a learned world model or a complete architecture for general intelligence. It is a software-systems experiment in maintaining coherent machine operation across observation, action, consequence, and time. - -## What The Existing Implementation Actually Contains +The unit of work is a **state transition**, not a chat response. -The historical Foundry implementation already provides concrete machinery for this experiment: +State is a representation derived from observations, not guaranteed ground truth. A verification decision is only as strong as the checks and evidence behind it. Preserving a snapshot also does not, by itself, prove that it still matches the environment later. -- a typed run-state machine; -- isolated git worktrees for actions; -- structured planning artifacts; -- model/provider routing; -- deterministic build, test, lint, and schema verification; -- independent diff review; -- persistent run events and artifacts; -- PostgreSQL-backed run state; -- Redis-backed work queues; -- evidence and extraction contracts; -- evaluation infrastructure; -- deterministic hooks for policy enforcement; -- retry, cancellation, and failure states. +A planner may use a language model, deterministic logic, or another reasoning mechanism. The generic loop is expressed through interfaces; the concrete provider and environment implementations remain limited and experimental. -Some originally planned paths remain incomplete. In particular, parts of the extraction/batch pipeline are still Phase 1 stubs. The repository should therefore be read as a working experimental system with unfinished surfaces, not as a completed general architecture. +## Architecture -## Historical Implementation +The repository contains three related layers, not a completed rewrite. -The codebase still uses its original **Foundry** terminology and contains Unicorn-specific adapters, schemas, task types, and documentation. Those are retained for now because they are evidence of how the experiment emerged. +| Layer | Responsibility | Current implementation | +| --- | --- | --- | +| Transition core | Coordinate observation, planning, action, verification, and outcome recording | `TransitionEngine` and capability interfaces | +| Foundry adapter | Connect the general interfaces to the original software-engineering environment | Git worktrees, `AgentRunner`, code verification, review, artifact storage | +| Historical runtime | Preserve the existing API, database, event, and pull-request lifecycle | `RunEngine`, FastAPI, PostgreSQL, Redis, workers | -The current restructuring deliberately starts with the **conceptual boundary** before rewriting the runtime: +The historical runtime does not yet delegate its complete lifecycle to the transition core. Likewise, accepting an outcome is not the same as publishing, merging, or deploying a change. -```text -historical implementation generalized interpretation - -Unicorn state → environment state -Unicorn canon → state/evidence contracts -Claude → intelligence provider -Foundry run → controlled state transition -git worktree → isolated action environment -verification → transition validation -review → independent evaluation -run artifacts → durable transition evidence -PR → one possible action outcome -``` +The public name is **Continuity**. Python imports still use `foundry`, the distribution remains `unicorn-foundry`, and historical configuration names remain unchanged. This introduction does not rename packages or break existing imports. -The long-term architecture should not require Claude, GitHub, source code, or Unicorn. Those are properties of the first implementation, not invariants of UCF. +## Evidence and status -## Architectural Invariants +The following is a dated record, not a claim that every planned capability is available. -1. **State is explicit.** The system should not depend on a model reconstructing its entire operating reality from a prompt. -2. **Actions produce transitions.** Work is understood as movement from a known state to a resulting state. -3. **Evidence survives inference.** Claims about what happened should remain traceable to observations and artifacts. -4. **Execution is controlled.** Intelligence proposes or performs actions inside explicit boundaries. -5. **Verification is separate from generation.** Producing an action and establishing that it worked are different operations. -6. **History is durable.** Meaningful transitions leave events and artifacts behind. -7. **Models are replaceable participants.** UCF should not depend conceptually on one provider, model family, or reasoning architecture. -8. **Continuity is a systems property.** Long-horizon coherence comes from the loop around intelligence as well as from intelligence itself. +**Merged baseline:** commit `2639b8ebeeb485950a8faed17491b03ff440b354`, validated on 25 September 2026. [GitHub Actions run 36120929154](https://github.com/sinethxyz/UCf/actions/runs/36120929154) passed installation, compilation, targeted Ruff checks, 21 selected foundation/adapter tests, and the full 495-test suite. The selected tests are included in the total. The suite emitted 2,774 warnings. -## Current Direction +The adapter integration test uses a real temporary Git repository, real worktree isolation, real state observation, and local outcome storage. Model behaviour and verifier results are deterministic test substitutes. This establishes an integration boundary, not reliable live-model autonomy. -This repository is being reopened as UCF rather than maintained as an active Unicorn Foundry product. +**Pending reliability work:** [PR #6](https://github.com/sinethxyz/UCf/pull/6) preserves retrievable patches and reports before cleanup, adds failure records and fresh-state checks, and tests journal reload and patch replay. Its branch passed 525 tests, including a 51-test selected subset, in [run 36138567006](https://github.com/sinethxyz/UCf/actions/runs/36138567006). At preparation of this introduction, that PR is **open and unmerged**. Those improvements must not be attributed to the merged baseline. -A provider-neutral UCF foundation now lives alongside the historical Foundry runtime: +In particular, the baseline adapter can retain a patch checksum without retaining the patch itself before cleanup. That gap is one reason the evidence-retention work must precede claims about durable continuation. -- `IntelligenceProvider` separates orchestration from a concrete model vendor; -- `ExecutionEnvironment` separates isolated execution from Git worktrees; -- provider-neutral transition contracts represent state, evidence, actions, observations, verification, and outcomes; -- `TransitionEngine` closes a state → action → observation → verification → outcome loop; -- `TransitionJournal` requires the verified outcome to survive the call; -- `FoundryTransitionRuntime` maps the historical planner, implementer, verifier, migration guard, worktree manager, and artifact store onto those interfaces; -- integration tests exercise that adapter with a real Git repository and real worktree isolation. +## Run the tests -The abstraction is therefore exercised by the original machinery, not only by fakes. The remaining P0 boundary is **runtime convergence**: the backwards-compatible `RunEngine` still owns the old database/event/PR lifecycle and must delegate its core transition work to the UCF path. PR creation should become publication after an accepted transition rather than the definition of completion. +From a checked-out copy of this repository, with **Python 3.12+ and Git**: -See [RETROSPECTIVE.md](RETROSPECTIVE.md) for the present-day interpretation, [docs/runtime-decoupling-audit.md](docs/runtime-decoupling-audit.md) for the migration map, and [docs/architecture.md](docs/architecture.md) for the original Foundry architecture specification. +```bash +python -m venv .venv +source .venv/bin/activate +python -m pip install -e ".[dev]" -## Repository Map +# Selected transition and adapter tests. +python -m pytest -q tests/unit/test_transition_models.py tests/unit/runtime tests/unit/orchestration/test_agent_runner.py -```text -UCf/ -├── README.md # current UCF thesis and status -├── RETROSPECTIVE.md # historical interpretation boundary -├── CLAUDE.md # guidance for future agents/engineering -├── docs/ -│ ├── ucf-architecture.md # generalized architecture mapping -│ ├── runtime-decoupling-audit.md # migration map and remaining coupling -│ └── architecture.md # original Unicorn Foundry specification -├── foundry/ -│ ├── contracts/ -│ │ ├── transition_models.py # state, evidence, action, outcome contracts -│ │ └── ... # historical Foundry contracts -│ ├── runtime/ -│ │ ├── interfaces.py # observer/planner/executor/verifier/journal -│ │ └── transition_engine.py # provider-neutral state-transition loop -│ ├── adapters/ -│ │ └── foundry_transition.py # historical Foundry -> UCF capability bridge -│ ├── environments/ -│ │ ├── base.py # ExecutionEnvironment contract -│ │ ├── git_worktree.py # concrete execution environment adapter -│ │ └── git_observer.py # explicit before/after Git state -│ ├── providers/ -│ │ ├── base.py # IntelligenceProvider contract -│ │ └── claude_*.py # historical/default Claude adapters -│ ├── orchestration/ # historical Foundry run machinery -│ ├── verification/ # historical deterministic code verification -│ ├── git/ # historical Git/PR action surface -│ ├── tasks/ # historical Foundry task implementations -│ ├── db/ # historical run persistence -│ └── storage/ -│ └── transition_journal.py # durable UCF outcome adapter -├── app/ # historical FastAPI control plane -├── workers/ # historical background workers -├── canon/ # historical Unicorn domain contracts -├── hooks/ # historical deterministic safeguards -├── tests/ -│ └── unit/runtime/ # provider-neutral transition-loop tests -└── .github/workflows/ - └── ucf-foundation.yml # compile, lint, foundation + regression tests +# Full repository regression suite. +python -m pytest -q ``` -The repository intentionally contains both the generalized UCF foundation and the historical Foundry implementation. The historical directories are not being renamed away until their behavior has been migrated through exercised UCF interfaces. - -## Historical Foundry Runtime - -The sections below document the original concrete runtime. They are retained because they show how the systems problem was first implemented; they should not be read as requirements of the generalized UCF architecture. +These tests do not require live model calls or deployment. Installation downloads dependencies. The historical service setup is preserved in [LEGACY_FOUNDRY.md](LEGACY_FOUNDRY.md); it is separate from this test-only starting point. -## Historical Foundry Task Types +## What this does not establish +This repository does not demonstrate a learned world model, general intelligence, or continual model learning. It does not establish crash-resume, exactly-once actions, comprehensive verification coverage, or production readiness. -| Task Type | Description | Model Routing | -|-----------|-------------|---------------| -| `endpoint_build` | Build new API endpoints in unicorn-app | Sonnet (plan/impl), Opus (review) | -| `feature_slice` | Implement feature slices across the stack | Sonnet (plan/impl), Opus (review) | -| `bug_fix` | Diagnose and fix bugs with regression tests | Sonnet (plan/impl), Opus (review) | -| `refactor` | Refactor code with safety verification | Sonnet (plan/impl), Opus (review) | -| `migration_plan` | Database migration planning and execution | Opus (plan/review/guard) | -| `architecture_review` | Architecture-level review and analysis | Opus (plan/review) | -| `review_diff` | Standalone independent diff review | Opus (review) | -| `extraction_batch` | Batch signal-to-event extraction | Sonnet (extract), Haiku (classify) | -| `evidence_classification` | Classify evidence strength levels | Haiku (classify) | -| `eval_run` | Run evaluation suites against model outputs | Sonnet (evaluate) | -| `canon_update` | Update shared schemas and domain docs | Opus (plan/review), Sonnet (impl) | +The historical Git environment still starts from `HEAD` rather than honouring every requested base reference. Some verification and extraction paths are partial. `REQUEST_CHANGES` is advisory under the inherited Foundry policy, so an accepted transition is not necessarily an unconditional review approval. These are limitations to resolve, not details to hide behind a test count. -## Historical Foundry Run Lifecycle - -``` -queued → creating_worktree → planning → implementing → verifying - → verification_passed → reviewing → pr_opened → completed -``` - -Failure states: `plan_failed`, `verification_failed`, `review_failed`, `cancelled`, `errored` - -Failed runs in `plan_failed`, `verification_failed`, or `review_failed` can be retried (transitions back to `queued`). Any non-terminal run can be cancelled. - -## Historical Foundry API Endpoints - -| Method | Path | Description | -|--------|------|-------------| -| `GET` | `/v1/health` | Health check | -| `POST` | `/v1/runs` | Submit a new task run | -| `GET` | `/v1/runs/{id}` | Get run status and metadata | -| `GET` | `/v1/runs/{id}/events` | Get run events (state transitions) | -| `GET` | `/v1/runs/{id}/artifacts` | List run artifacts | -| `POST` | `/v1/runs/{id}/cancel` | Cancel an in-progress run | -| `POST` | `/v1/runs/{id}/retry` | Retry a failed run | -| `POST` | `/v1/reviews` | Request an independent review | -| `POST` | `/v1/specs/plan` | Generate a plan from a spec | -| `POST` | `/v1/patches/apply` | Apply a patch to a worktree | -| `POST` | `/v1/batches/extract` | Start a batch extraction job | -| `GET` | `/v1/batches/{id}` | Get batch status | -| `GET` | `/v1/batches/{id}/results` | Get extraction results | -| `POST` | `/v1/evals/run` | Run an evaluation suite | -| `GET` | `/v1/evals/{id}` | Get eval results | -| `POST` | `/v1/worktrees/cleanup` | Clean up stale worktrees | - -## Historical Foundry Subagents - -| Agent | Role | Model | -|-------|------|-------| -| **Planner** | Produces structured `PlanArtifact` with file-level steps | Sonnet / Opus | -| **Backend Implementer** | Executes plans in Go (unicorn-app API) | Sonnet | -| **Frontend Implementer** | Executes plans in TypeScript (Next.js) | Sonnet | -| **Reviewer** | Independent diff review (never sees the plan) | Opus | -| **Extractor** | Signal-to-event structured extraction | Sonnet | -| **Migration Guard** | High-scrutiny review for migrations/auth/infra | Opus | -| **Repo Explorer** | Read-only codebase reconnaissance | Haiku | - -## Historical Foundry Claude Code Skills - -| Skill | Description | -|-------|-------------| -| `spec-to-plan` | Generate a structured implementation plan from a spec | -| `endpoint-generator` | Scaffold a new API endpoint end-to-end | -| `safe-refactor` | Refactor code with automatic verification | -| `review-diff` | Review any diff independently | -| `issue-to-pr` | Resolve a GitHub issue from triage to PR | -| `extract-signals` | Run signal extraction pipeline | -| `run-eval` | Execute evaluation suites | - -## Historical Foundry Hooks (Deterministic Enforcement) - -| Hook | Trigger | Purpose | -|------|---------|---------| -| `block_secrets.sh` | Pre: Read, Edit, Write | Block access to `.env`, `*.key`, `*secrets*`, etc. | -| `block_protected_paths.sh` | Pre: Edit, Write | Guard `migrations/`, `auth/`, `infra/`, Docker files | -| `require_plan.sh` | Pre: Edit, Write | Block edits without a stored plan | -| `verify_after_edit.sh` | Post: Edit, Write | Run verification after file modifications | -| `log_tool_call.sh` | Post: all tools | Log every tool invocation for auditability | - -## Historical Foundry MCP Profiles - -Runs can be scoped to specific MCP server access: - -| Profile | Servers | Use Case | -|---------|---------|----------| -| `none` | — | Default, no external access | -| `github_only` | GitHub | Code builds, PR workflows | -| `github_postgres_readonly` | GitHub + Postgres (read-only) | Research with data access | -| `research_full` | GitHub + Postgres (read-only) | Full research capabilities | -| `app_build_minimal` | GitHub | Minimal build access | - -## Historical Foundry Model Routing - -| Model | Use Case | -|-------|----------| -| **Opus 4.6** | Architecture, critical planning, review, migration guard, red-teaming | -| **Sonnet 4.6** | Implementation, structured extraction, endpoint building, evals | -| **Haiku 4.5** | Classification, tagging, reconnaissance, simple preprocessing | - -Routing is defined in `foundry/orchestration/model_router.py`. Override via `model_override` in task requests when justified. - -## Historical Foundry Database Schema - -PostgreSQL tables managed via Alembic: - -| Table | Purpose | -|-------|---------| -| `runs` | Run lifecycle records (state, branch, PR URL, metadata) | -| `run_events` | State transition events with timing and token usage | -| `run_artifacts` | Artifact metadata (type, storage path, checksum) | -| `worktrees` | Git worktree tracking and cleanup state | -| `batch_jobs` | Batch extraction/processing jobs | -| `batch_items` | Individual items within batch jobs | -| `eval_runs` | Evaluation run records with metrics | -| `verification_results` | Deterministic verification step results | - -## Prerequisites - -- Python 3.12+ -- Docker and Docker Compose -- Git - -## Setup - -```bash -# Start Postgres and Redis -docker compose up -d postgres redis - -# Install dependencies -pip install -e ".[dev]" - -# Run database migrations -alembic upgrade head +## Origin -# Run the API server -uvicorn app.main:app --host 0.0.0.0 --port 8000 -``` +I encountered the problem by trying to build the system. -Or run everything via Docker: +While working on Unicorn, I was exploring how signals and evidence could become machine-readable state. UCF, initially called Unicorn Foundry, explored the complementary execution problem: plan a change, carry it out in an isolated environment, verify it, review it, and preserve a record of the result. -```bash -export ANTHROPIC_API_KEY= -export GITHUB_TOKEN= -docker compose up +```text +Unicorn: signals → evidence → state → legibility +UCF: state → intent → plan → action → verification → outcome ``` -This starts the API server, run worker, and batch worker with shared Postgres and Redis. - -The API is available at `http://localhost:8000`. Health check: `GET /v1/health`. +Unicorn was discontinued. The engineering question outlived the application that produced it. -## Configuration +Continuity is the public name for reopening that experiment. The origin was a practical systems problem; this framing is a later explanation of what I was trying to investigate. It is not a research-priority claim or an attempt to make the original implementation appear more complete than it was. -All settings use the `FOUNDRY_` env prefix (via pydantic-settings): +The earlier commits, [original architecture specification](docs/architecture.md), and [retrospective](RETROSPECTIVE.md) remain intact. [LEGACY_FOUNDRY.md](LEGACY_FOUNDRY.md) preserves the pre-Continuity README verbatim from the merged baseline, including its historical operational documentation. It is a snapshot, not an updated capability guarantee. -| Variable | Default | Description | -|----------|---------|-------------| -| `FOUNDRY_DATABASE_URL` | `postgresql+asyncpg://foundry:foundry@localhost:5432/foundry` | PostgreSQL connection | -| `FOUNDRY_REDIS_URL` | `redis://localhost:6379` | Redis connection | -| `FOUNDRY_ANTHROPIC_API_KEY` | — | Anthropic API key | -| `FOUNDRY_GITHUB_TOKEN` | — | GitHub token for PR operations | -| `FOUNDRY_MAX_CONCURRENT_RUNS` | `5` | Max parallel run executions | -| `FOUNDRY_MAX_RETRIES_PER_RUN` | `3` | Max retry attempts per run | -| `FOUNDRY_WORKTREE_BASE_PATH` | `/tmp/foundry-worktrees` | Worktree storage directory | -| `FOUNDRY_LOG_LEVEL` | `INFO` | Log verbosity | +## Next milestones -## Development - -```bash -# Run tests -pytest +The immediate sequence is to review the pending evidence-retention work, honour explicit base-state requirements, make verification coverage and review acceptance unambiguous, and then converge the historical runtime onto the transition loop. -# Lint and type check -ruff check . -mypy . +After that, longer-running, failure-injected and bounded live-model evaluations can test whether the architecture improves continuity in practice. Those evaluations have not been demonstrated here. -# Run a task via CLI -python scripts/run_task.py --type endpoint_build --spec "Add GET /v1/companies/{id}/timeline" +The implementation should earn broader claims rather than assume them in advance. -# Seed the database with test data -python scripts/seed_db.py +## Repository guide -# Export artifacts for inspection -python scripts/export_artifacts.py --run-id +```text +foundry/contracts/transition_models.py state, evidence, actions, outcomes +foundry/runtime/ generic transition loop and interfaces +foundry/adapters/ historical Foundry compatibility bridge +foundry/environments/ Git environment and observation +foundry/providers/ provider interface and implementations +foundry/storage/ artifact storage and outcome journal +foundry/orchestration/ historical run lifecycle +app/ and workers/ historical service entry points +tests/unit/runtime/ transition and adapter tests ``` -## Tech Stack - -| Component | Technology | -|-----------|-----------| -| API Framework | FastAPI 0.115+ | -| Data Validation | Pydantic 2.9+ | -| Database ORM | SQLAlchemy 2.0+ (async) | -| Database Driver | asyncpg | -| Migrations | Alembic | -| Task Queue | Redis 5.2+ | -| AI Provider | Anthropic SDK 0.40+ (Agent SDK, Messages API, Batch API) | -| HTTP Client | httpx | -| Object Storage | boto3 (S3-compatible) | -| Logging | python-json-logger | -| Build System | hatchling | -| Linting | ruff | -| Type Checking | mypy (strict mode) | -| Testing | pytest + pytest-asyncio | - -## Historical Foundry Language Boundaries - -- **Python** — this repo (Foundry). All orchestration, extraction, eval code. -- **Go** — unicorn-app backend. Foundry writes Go code into unicorn-app via PRs. -- **TypeScript** — unicorn-app frontend. Foundry writes TS code into unicorn-app via PRs. +See the [architecture mapping](docs/ucf-architecture.md), [runtime decoupling audit](docs/runtime-decoupling-audit.md), and [publication notes](docs/publication.md) for the implementation history, migration boundaries, and approved public identity. -Foundry never mixes languages. The appropriate implementer subagent is selected based on the target. +## Licence -## License +The existing notice remains: **Internal use only. Not licensed for external distribution.** -Internal use only. Not licensed for external distribution. +This naming and documentation pass does not grant a new licence. A public-release/reuse licence requires a separate owner decision; the project is not being announced as open source in this pass. diff --git a/docs/publication.md b/docs/publication.md new file mode 100644 index 0000000..6fc8248 --- /dev/null +++ b/docs/publication.md @@ -0,0 +1,101 @@ +# Continuity: publication notes + +Prepared 25 September 2026. These are the approved public identity and launch boundaries, not confirmation that GitHub settings have been changed or an announcement has been posted. + +## Identity + +**Display name:** Continuity + +**Repository name:** `continuity` + +**Intended repository:** `sinethxyz/continuity` + +**GitHub About description:** + +> An experimental runtime for persistent machine intelligence across state, action, verification, and time. + +**README tagline:** + +> An experiment in intelligence through time. + +**Core sentence:** + +> The model is a participant in the loop, not the loop itself. + +**Topics:** + +```text +ai +agents +state-machines +llm +agent-infrastructure +ai-systems +orchestration +verification +continuity +machine-intelligence +``` + +Persistent machine intelligence describes the research objective. The evidence currently supports a software-systems experiment with scoped tests, not a proven general or continuously learning intelligence. + +## Naming boundary + +Continuity is the public name. UCF and Unicorn Foundry remain historical names. Do not relabel the original commits or retrofit dates into the origin story. The claim is that the engineering problem was encountered while building the system, not that this work originated another researcher's architecture. + +Python imports stay under `foundry`. The distribution stays `unicorn-foundry`. Environment variable prefixes, workflow identifiers, historical specifications, and internal contracts are unchanged. There is no new package release in this naming pass. + +[LEGACY_FOUNDRY.md](../LEGACY_FOUNDRY.md) preserves the old README verbatim from commit `2639b8ebeeb485950a8faed17491b03ff440b354` (blob `7caeb132210e40d8f98ed587204eef41cb03d2dd`). Its root location preserves the original relative links. + +## Owner-admin actions still required + +The available GitHub connection supports repository files and PRs, but does not expose a repository rename or About/topics update action. Those settings have not been changed by this documentation pass. + +Apply the repository name, About description, and topics above using the owner's GitHub controls, confirming that the chosen name is available. Keep the existing visibility; this pass does not request a visibility change. Do not invent a project homepage or package URL. + +After the rename, verify the canonical repository URL, old inbound links, open PRs, and any relevant integrations. Update local Git remotes after confirming the new URL. Do not create a replacement repository or discard the existing history. + +Repository settings are separate from Git commits; putting `Continuity` in the README cannot rename the repository. + +## Draft announcement + +Not posted. Add the verified repository URL when publishing. + +> The model is not the system. +> +> While building Unicorn + UCF, I kept encountering the same problem: a capable model could still sit inside a discontinuous system. +> +> I'm reopening that experiment as Continuity: a systems experiment in explicit state, controlled action, verification, and what survives the next interaction. +> +> The model is a participant in the loop, not the loop itself. + +Do not add claims about being first, a learned world model, general intelligence, production readiness, or a year of development without supporting dated artifacts. Do not describe deterministic model substitutes as live-model validation. + +## Evidence boundaries + +At preparation: + +| Revision | Scope | Evidence | +| --- | --- | --- | +| Merged main `2639b8e` | Transition foundation and Foundry adapter | 495 full-suite tests; 21 selected tests included in the total | +| Open [PR #6](https://github.com/sinethxyz/UCf/pull/6), head `8a421e5` | Evidence retention, failure records, state checks, reload/replay tests | 525 full-suite tests; 51 selected tests included in the total | +| This public-introduction branch | Naming and documentation only | No new runtime capability or model evaluation | + +Sources: [baseline CI](https://github.com/sinethxyz/UCf/actions/runs/36120929154) and [PR #6 CI](https://github.com/sinethxyz/UCf/actions/runs/36138567006). Both test runs reported 2,774 warnings. Recheck the actual publication revision before using any count in an announcement. + +The pending PR's code and test evidence do not belong to main until that PR is approved and merged. Keep this rebrand separate from that approval. Renaming the repository does not fix the base-reference limitation, complete verifier coverage, migrate RunEngine, or provide crash recovery. + +## Licence decision + +The pre-rebrand README says: **Internal use only. Not licensed for external distribution.** This pass preserves that notice and does not choose a new licence. + +Before presenting this as an open-source release or inviting external reuse, the owner must explicitly decide the licensing terms. Do not add an MIT, Apache, or other licence merely because the repository is public. + +## Launch checklist + +- [ ] Apply and verify the repository name and About/topics settings. +- [ ] Review and approve the documentation-only rebrand separately; no merge is performed by this pass. +- [ ] Review PR #6 separately; leave it unmerged until explicitly approved. +- [ ] Resolve the public-release/reuse licence decision. +- [ ] Recheck the final published commit, links, CI evidence, and capability statements. +- [ ] Publish the announcement only after the desired public state is confirmed. From 4c6223da1780dc06a1a799c82be8b316cf7cc0d4 Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:25:49 +0100 Subject: [PATCH 3/7] docs: update Continuity public status and AGPL licence --- README.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index ba6e692..a28f3b4 100644 --- a/README.md +++ b/README.md @@ -63,13 +63,11 @@ The public name is **Continuity**. Python imports still use `foundry`, the distr The following is a dated record, not a claim that every planned capability is available. -**Merged baseline:** commit `2639b8ebeeb485950a8faed17491b03ff440b354`, validated on 25 September 2026. [GitHub Actions run 36120929154](https://github.com/sinethxyz/UCf/actions/runs/36120929154) passed installation, compilation, targeted Ruff checks, 21 selected foundation/adapter tests, and the full 495-test suite. The selected tests are included in the total. The suite emitted 2,774 warnings. +**Merged baseline:** commit `6cc52e5e8dd22bccf6d00b7e78bb542f0538f8a3`, validated on 25 September 2026. [GitHub Actions run 36140729000](https://github.com/sinethxyz/continuity/actions/runs/36140729000) passed installation, compilation, targeted Ruff checks, the 51-test foundation/adapter/integrity subset, and the full 525-test regression suite. The selected tests are included in the total. The suite still emits existing warnings; passing tests are evidence for the exercised boundaries, not a production-readiness claim. -The adapter integration test uses a real temporary Git repository, real worktree isolation, real state observation, and local outcome storage. Model behaviour and verifier results are deterministic test substitutes. This establishes an integration boundary, not reliable live-model autonomy. +The adapter and integrity tests use real temporary Git repositories, worktree isolation, state observation, local artifact storage, patch capture/replay, and fresh-process journal reload. Model behaviour and verifier results remain deterministic test substitutes. This establishes a stronger systems integration boundary, not reliable live-model autonomy. -**Pending reliability work:** [PR #6](https://github.com/sinethxyz/UCf/pull/6) preserves retrievable patches and reports before cleanup, adds failure records and fresh-state checks, and tests journal reload and patch replay. Its branch passed 525 tests, including a 51-test selected subset, in [run 36138567006](https://github.com/sinethxyz/UCf/actions/runs/36138567006). At preparation of this introduction, that PR is **open and unmerged**. Those improvements must not be attributed to the merged baseline. - -In particular, the baseline adapter can retain a patch checksum without retaining the patch itself before cleanup. That gap is one reason the evidence-retention work must precede claims about durable continuation. +The reliability pass now preserves retrievable plans, patches, verification/review reports, and outcome records before cleanup; records failure paths; checks fresh state against supplied preconditions; and exercises replay/reload behavior. See [evidence-retention.md](docs/evidence-retention.md) for the exact scope and limitations. ## Run the tests @@ -114,7 +112,7 @@ The earlier commits, [original architecture specification](docs/architecture.md) ## Next milestones -The immediate sequence is to review the pending evidence-retention work, honour explicit base-state requirements, make verification coverage and review acceptance unambiguous, and then converge the historical runtime onto the transition loop. +The immediate sequence is to honour explicit base-reference requirements, make verification coverage and review acceptance unambiguous, and then converge the historical runtime onto the transition loop. After that, longer-running, failure-injected and bounded live-model evaluations can test whether the architecture improves continuity in practice. Those evaluations have not been demonstrated here. @@ -138,6 +136,8 @@ See the [architecture mapping](docs/ucf-architecture.md), [runtime decoupling au ## Licence -The existing notice remains: **Internal use only. Not licensed for external distribution.** +Continuity is licensed under the **GNU Affero General Public License v3.0 only (AGPL-3.0-only)**. + +Copyright © 2026 Sineth Madduma. -This naming and documentation pass does not grant a new licence. A public-release/reuse licence requires a separate owner decision; the project is not being announced as open source in this pass. +See [LICENSE](LICENSE) for the complete licence text. The AGPL includes source-availability obligations for modified versions offered to users over a network; anyone deploying or redistributing modified versions should review the licence terms that apply to their use. From 3903ff19e4bac2336a02f49383595e085917987b Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:26:03 +0100 Subject: [PATCH 4/7] docs: finalize Continuity publication state --- docs/publication.md | 34 ++++++++++++++-------------------- 1 file changed, 14 insertions(+), 20 deletions(-) diff --git a/docs/publication.md b/docs/publication.md index 6fc8248..f7b26fd 100644 --- a/docs/publication.md +++ b/docs/publication.md @@ -47,15 +47,11 @@ Python imports stay under `foundry`. The distribution stays `unicorn-foundry`. E [LEGACY_FOUNDRY.md](../LEGACY_FOUNDRY.md) preserves the old README verbatim from commit `2639b8ebeeb485950a8faed17491b03ff440b354` (blob `7caeb132210e40d8f98ed587204eef41cb03d2dd`). Its root location preserves the original relative links. -## Owner-admin actions still required +## Repository settings -The available GitHub connection supports repository files and PRs, but does not expose a repository rename or About/topics update action. Those settings have not been changed by this documentation pass. +The repository has been renamed to `sinethxyz/continuity`, and the approved About description and topics have been applied by the owner. -Apply the repository name, About description, and topics above using the owner's GitHub controls, confirming that the chosen name is available. Keep the existing visibility; this pass does not request a visibility change. Do not invent a project homepage or package URL. - -After the rename, verify the canonical repository URL, old inbound links, open PRs, and any relevant integrations. Update local Git remotes after confirming the new URL. Do not create a replacement repository or discard the existing history. - -Repository settings are separate from Git commits; putting `Continuity` in the README cannot rename the repository. +The existing Git history is preserved. Local clones should use the canonical remote `https://github.com/sinethxyz/continuity.git`. ## Draft announcement @@ -77,25 +73,23 @@ At preparation: | Revision | Scope | Evidence | | --- | --- | --- | -| Merged main `2639b8e` | Transition foundation and Foundry adapter | 495 full-suite tests; 21 selected tests included in the total | -| Open [PR #6](https://github.com/sinethxyz/UCf/pull/6), head `8a421e5` | Evidence retention, failure records, state checks, reload/replay tests | 525 full-suite tests; 51 selected tests included in the total | -| This public-introduction branch | Naming and documentation only | No new runtime capability or model evaluation | +| Merged main `6cc52e5` | Transition foundation, Foundry adapter, evidence retention, failure records, state checks, reload/replay tests | 525 full-suite tests; 51 selected tests included in the total | +| This public-introduction branch | Naming, licensing and documentation | No new model capability or deployment | -Sources: [baseline CI](https://github.com/sinethxyz/UCf/actions/runs/36120929154) and [PR #6 CI](https://github.com/sinethxyz/UCf/actions/runs/36138567006). Both test runs reported 2,774 warnings. Recheck the actual publication revision before using any count in an announcement. +Source: [main CI](https://github.com/sinethxyz/continuity/actions/runs/36140729000). The run completed successfully on the merged reliability baseline. Recheck the final publication revision before quoting test counts. -The pending PR's code and test evidence do not belong to main until that PR is approved and merged. Keep this rebrand separate from that approval. Renaming the repository does not fix the base-reference limitation, complete verifier coverage, migrate RunEngine, or provide crash recovery. +Renaming and licensing the repository do not fix the base-reference limitation, complete verifier coverage, migrate RunEngine, provide crash recovery, or establish production readiness. -## Licence decision +## Licence -The pre-rebrand README says: **Internal use only. Not licensed for external distribution.** This pass preserves that notice and does not choose a new licence. +The owner selected **GNU Affero General Public License v3.0 only (AGPL-3.0-only)** for Continuity. The repository includes the complete licence text in `LICENSE`; package metadata uses the same SPDX expression. -Before presenting this as an open-source release or inviting external reuse, the owner must explicitly decide the licensing terms. Do not add an MIT, Apache, or other licence merely because the repository is public. +The pre-rebrand `LEGACY_FOUNDRY.md` remains a historical snapshot and may contain the former internal-use notice. That snapshot does not override the current root licence. ## Launch checklist -- [ ] Apply and verify the repository name and About/topics settings. -- [ ] Review and approve the documentation-only rebrand separately; no merge is performed by this pass. -- [ ] Review PR #6 separately; leave it unmerged until explicitly approved. -- [ ] Resolve the public-release/reuse licence decision. -- [ ] Recheck the final published commit, links, CI evidence, and capability statements. +- [x] Apply and verify the repository name and About/topics settings. +- [x] Merge and validate the evidence-retention reliability pass. +- [x] Select AGPL-3.0-only and add repository/package licence metadata. +- [ ] Recheck the final public-introduction merge commit, links, CI evidence, and capability statements. - [ ] Publish the announcement only after the desired public state is confirmed. From 52712d84fd62e7fc77547892740e89c11e8a7f86 Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:26:05 +0100 Subject: [PATCH 5/7] docs: align project guidance with merged reliability baseline --- CLAUDE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index c2fbaa8..9e7cfe1 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -6,9 +6,9 @@ This is a documentation rebrand, not a package or runtime migration. Keep `foundry` imports, the `unicorn-foundry` distribution name, `FOUNDRY_*` configuration, workflow identifiers, historical documents, and existing technical contracts unchanged unless a separate task explicitly migrates them. -The original README is preserved verbatim in `LEGACY_FOUNDRY.md`. The public description, topics, draft announcement, and remaining launch decisions live in `docs/publication.md`. A documentation commit does not change GitHub repository settings or grant an open-source licence. +The original README is preserved verbatim in `LEGACY_FOUNDRY.md`. The public description, topics, draft announcement, and remaining launch decisions live in `docs/publication.md`. The repository is publicly named Continuity and is licensed under AGPL-3.0-only. Preserve the historical UCF/Foundry names only where they describe the implementation history. -Distinguish merged capabilities from unmerged PR work in every public claim. At this rebrand's preparation, PR #6 remains open and unmerged. Do not merge it or this documentation PR as part of the naming pass. +Distinguish merged capabilities from future or experimental work in every public claim. The evidence-retention reliability pass is merged; do not describe later milestones as completed until their own evidence exists. The implementation guidance below retains its UCF/Foundry terminology; the discontinued Unicorn product is historical context, not a reason to revive it. From b4b8c3b22ca3d5db4faf9891804192f889d02fb1 Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:26:07 +0100 Subject: [PATCH 6/7] build: declare AGPL-3.0-only package licence --- pyproject.toml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 2dc7071..2747d55 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,8 +1,9 @@ [project] name = "unicorn-foundry" version = "0.1.0" -description = "UCF experiment in persistent machine operation across changing state" +description = "An experimental runtime for persistent machine intelligence across state, action, verification, and time." requires-python = ">=3.12" +license = "AGPL-3.0-only" dependencies = [ "fastapi>=0.115.0", "uvicorn[standard]>=0.30.0", From 85dbdc4dbbc9ae949325b86f14477540919ef2dd Mon Sep 17 00:00:00 2001 From: sineth madduma <149978246+sinethxyz@users.noreply.github.com> Date: Fri, 25 Sep 2026 14:26:09 +0100 Subject: [PATCH 7/7] legal: license Continuity under AGPL-3.0-only --- LICENSE | 235 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 235 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..0c97efd --- /dev/null +++ b/LICENSE @@ -0,0 +1,235 @@ +GNU AFFERO GENERAL PUBLIC LICENSE +Version 3, 19 November 2007 + +Copyright (C) 2007 Free Software Foundation, Inc. + +Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. + + Preamble + +The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software. + +The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. + +When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. + +Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software. + +A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate. Many developers of free software are heartened and encouraged by the resulting cooperation. However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public. + +The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community. It requires the operator of a network server to provide the source code of the modified version running there to the users of that server. Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version. + +An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals. This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license. + +The precise terms and conditions for copying, distribution and modification follow. + + TERMS AND CONDITIONS + +0. Definitions. + +"This License" refers to version 3 of the GNU Affero General Public License. + +"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. + +"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. + +To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. + +A "covered work" means either the unmodified Program or a work based on the Program. + +To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. + +To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. + +An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. + +1. Source Code. +The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. + +A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. + +The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. + +The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those +subprograms and other parts of the work. + +The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. + +The Corresponding Source for a work in source code form is that same work. + +2. Basic Permissions. +All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. + +You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. + +Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. + +3. Protecting Users' Legal Rights From Anti-Circumvention Law. +No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. + +When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. + +4. Conveying Verbatim Copies. +You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. + +You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. + +5. Conveying Modified Source Versions. +You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: + + a) The work must carry prominent notices stating that you modified it, and giving a relevant date. + + b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". + + c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. + + d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. + +A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. + +6. Conveying Non-Source Forms. +You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: + + a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. + + b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. + + c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. + + d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. + + e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. + +A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. + +A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. + +"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. + +If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). + +The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. + +Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. + +7. Additional Terms. +"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. + +When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. + +Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: + + a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or + + b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or + + c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or + + d) Limiting the use for publicity purposes of names of licensors or authors of the material; or + + e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or + + f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. + +All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. + +If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. + +Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. + +8. Termination. + +You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). + +However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. + +Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. + +Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. + +9. Acceptance Not Required for Having Copies. + +You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. + +10. Automatic Licensing of Downstream Recipients. + +Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. + +An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. + +You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. + +11. Patents. + +A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". + +A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. + +Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. + +In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. + +If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent +license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. + +If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. + +A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. + +Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. + +12. No Surrender of Others' Freedom. + +If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may +not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. + +13. Remote Network Interaction; Use with the GNU General Public License. + +Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software. This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph. + +Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License. + +14. Revised Versions of this License. + +The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. + +Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation. + +If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. + +Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. + +15. Disclaimer of Warranty. + +THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. + +16. Limitation of Liability. + +IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. + +17. Interpretation of Sections 15 and 16. + +If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. + +END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + +If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. + +To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. + + This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License for more details. + + You should have received a copy of the GNU Affero General Public License along with this program. If not, see . + +Also add information on how to contact you by electronic and paper mail. + +If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source. For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code. There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements. + +You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see .