---
id: overview
title: "Overview"
description: "Follow a Corp v1 project from Board approval through governed scope, delivery, deployment, and verified evidence."
---

import Drawio from '@theme/Drawio';
import overviewDiagram from '!!raw-loader!./diagrams/overview.drawio';

# Overview

Every approved Corp v1 project repeats the same high-level operating flow while keeping its own decisions and delivery boundary.

<Drawio content={overviewDiagram} title="Corp v1 project operating flow" toolbar="zoom layers lightbox" responsive maxHeight={720} />

## How projects operate

1. **Board approval** establishes the project purpose, code, lead, members, visibility, initial deliverable, and required resources.
2. **Scope** turns evidence-backed intent into Ideas, Epics, and Features. A human project member approves a Feature for solution work.
3. **Architecture** defines requirements, decisions, diagrams, and implementation Tasks without treating documentation scaffolding as an approved target design.
4. **Kanban** exposes unfinished work. A human project member explicitly admits an exact Task to Focus before Delivery may execute it.
5. **Delivery** implements through reviewable branches and pull requests; Gitea Actions validates the exact candidate.
6. **Releases** assess immutable artifacts, risk, rollback, deployment, and acceptance evidence.
7. **Verification** reads the deployed page or runtime back and updates durable project and governance records.

## Project-owned operating guidance

Each project adopts six channel skills and seven engineering skills into its dedicated skills/code-agent organization. Those copies preserve project naming, environment namespaces, repository links, authority decisions, and operating lessons. Central changes are compared and deliberately synchronized; they never silently overwrite project decisions.

Corp v1 projects and channels do **not** use cronjobs or scheduler jobs under the current approved model. Coordination is human- or event-driven.