chore(repo): initialize Cowork Local Gitea repository

docs/governance/definition-of-done.md

@@ -0,0 +1,25 @@
+# Definition of Done
+
+## Cowork-native feature
+
+A Cowork-native change is done when:
+
+- implementation is complete;
+- applicable tests pass;
+- documentation is updated when needed;
+- the Pull Request is reviewed;
+- the change is merged into the stable/default branch.
+
+## Core AI contribution
+
+A Core AI contribution is done only when its Pull Request is merged into Cowork Local. “Core AI finished coding” or “Core AI pre-review passed” is not Done.
+
+Required evidence:
+
+- Core issue reference;
+- Cowork Local Pull Request;
+- test/validation evidence;
+- Cowork reviewer;
+- merge commit or merge reference.
+
+Use one logical change per Pull Request. For example, TL-065, TL-146, and TL-148 Phase 1 require separate Pull Requests. Split large work into vertical, reviewable slices.

docs/governance/ownership.md

@@ -0,0 +1,28 @@
+# Repository Ownership
+
+## Cowork Team
+
+The Cowork Team owns:
+
+- product architecture;
+- Cowork runtime and platform behavior;
+- UI/UX;
+- releases;
+- the stable/default branch;
+- final Pull Request review and merge.
+
+## FSG AI Core Team
+
+The AI Core Team contributes selected generic capabilities, including:
+
+- MCP integrations;
+- agent capabilities;
+- orchestration tests;
+- model-routing and fallback tests;
+- security/evaluation integration;
+- Superpowers enhancements;
+- reusable platform improvements.
+
+AI Core is a contributor, not the owner of Cowork Local. It does not self-merge a contribution into the Cowork production branch before Cowork Team review.
+
+`OWNERS.yaml` records team-level ownership only. It intentionally contains no invented usernames and does not assume GitHub CODEOWNERS semantics in Gitea.

docs/governance/review-policy.md

@@ -0,0 +1,12 @@
+# Review Policy
+
+Normal Cowork changes follow the Cowork Team's reviewer policy.
+
+Core AI contributions require two review stages:
+
+1. Core AI internal/pre-review.
+2. Cowork Team final review and merge decision.
+
+Additional scrutiny is required for permissions, credentials, MCP write/exec, sandboxing, network access, TLS, customer/project isolation, security rules, model routing/fallback, and data deletion. These changes must not be auto-merged merely because automated checks pass.
+
+Branch protection should prevent force-push and deletion of the stable branch, prefer Pull Requests, and require CI after an Actions runner is available. Core AI contributors must not be configured as Cowork final approvers by process convention.