Organization governance: explicit estate and agent boundaries

ESTATE_GOVERNANCE_2026.md

@@ -0,0 +1,41 @@
+# Mind-Reply Estate Governance 2026
+
+The organization is a portfolio, not a monolith.
+
+## Classification
+
+Every repository belongs to exactly one primary class:
+
+`control | product | automation | communication | brand | template | experiment | archive`
+
+It must also declare visibility and authority.
+
+## Required repository metadata
+
+Each active repository should declare:
+
+- owner;
+- product/job to be done;
+- source-of-truth status;
+- public/private classification;
+- runtime/deployment target;
+- domain or intended domain;
+- data sensitivity;
+- automation dependencies;
+- release authority;
+- rollback path;
+- local product vocabulary.
+
+## Agent policy
+
+Repository agents are specialists. They may inherit common safety rules but must have a product-specific identity and vocabulary.
+
+No shared agent should assume that another repository has the same permissions, data or release process.
+
+## Public/private boundary
+
+Public repositories contain publishable product or open-source material. Private repositories contain owner operations, secrets, customer-sensitive data, private strategy and unfinished work. Personal repositories remain distinct from organization production.
+
+## Release principle
+
+A green build proves only that the tested build passed. A release is complete only when the deployed artifact, domain, critical user path and rollback path are verified.

PUBLIC_SURFACE_RULES.md

@@ -0,0 +1,27 @@
+# Public Surface Rules
+
+Public positioning should be deliberate, searchable and truthful.
+
+## Known canonical public surface
+
+- `mind-reply.com` — primary MindReply product/brand domain.
+
+Additional domains should only be recorded after ownership and DNS control are verified.
+
+## SEO contract
+
+Every public site should have:
+
+- one canonical URL per page;
+- descriptive title and meta description;
+- Open Graph/Twitter metadata;
+- sitemap and robots policy;
+- structured data where truthful and useful;
+- accessible headings and landmarks;
+- human-readable copy matching the actual product;
+- no keyword stuffing or invented claims;
+- a clear owner/contact route.
+
+## Brand separation
+
+Aurel, MindReply, A11-K, ReplyControl and future products may share engineering standards but must not share identical positioning, vocabulary or visual identity.

agents/repository-steward.md

@@ -0,0 +1,18 @@
+---
+name: repository-steward
+description: Organization-level repository governance specialist.
+---
+
+# Repository Steward
+
+Check the repository's declared role before changing it.
+
+Maintain the boundary between product code, automation, private operations, brand assets and experiments. Prefer PRs with evidence over broad refactors.
+
+When a repository is stale, first determine whether it is:
+- a migration source;
+- an experiment worth preserving;
+- a duplicate that should be archived;
+- a missing capability that belongs elsewhere.
+
+Do not merge repositories merely to reduce repository count. Reduce ambiguity instead.