AgenteLabs · Oct 27, 2026 · Oct 27, 2026 · Oct 27, 2026
diff --git a/.github/workflows/secret-scan.yml b/.github/workflows/secret-scan.yml
@@ -11,4 +11,4 @@ permissions:
 
 jobs:
   secrets:
-    uses: FlashyLabs/flashy-infra/.github/workflows/secret-scan-reusable.yml@main
+    uses: AgenteLabs/flashy-infra/.github/workflows/secret-scan-reusable.yml@main
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -2,7 +2,7 @@
 
 flashy-docs is the documentation hub for the Flashy ecosystem. This repository
 holds *explanations*; working code lives in
-[flashy-examples](https://github.com/flashylabs/flashy-examples). Link
+[flashy-examples](https://github.com/AgenteLabs/flashy-examples). Link
 generously between them.
 
 ## Before you open a PR

diff --git a/CONTRIBUTION-LADDER.md b/CONTRIBUTION-LADDER.md
@@ -396,8 +396,8 @@ Start → Bug Report (15 min)
 
 1. **Bugs:** Look for issues labeled `bug` or `help wanted`
 2. **Docs:** Search for `TODO` or broken links
-3. **Examples:** Check the [flashy-examples README](https://github.com/flashylabs/flashy-examples) for what exists and what is wanted
-4. **Features:** Ask in [GitHub Discussions](https://github.com/flashylabs/flashy-examples/discussions)
+3. **Examples:** Check the [flashy-examples README](https://github.com/AgenteLabs/flashy-examples) for what exists and what is wanted
+4. **Features:** Ask in [GitHub Discussions](https://github.com/AgenteLabs/flashy-examples/discussions)
 
 ### Before You Start
 
@@ -408,7 +408,7 @@ Start → Bug Report (15 min)
 ### Open Questions?
 
 - Comment on the issue you want to work on
-- Ask in [GitHub Discussions](https://github.com/flashylabs/flashy-examples/discussions)
+- Ask in [GitHub Discussions](https://github.com/AgenteLabs/flashy-examples/discussions)
 - Join our [Slack community](https://flashygroup.slack.com) (ask for link)
 
 ---

diff --git a/README.md b/README.md
@@ -14,7 +14,7 @@ Comprehensive guides and references for Ledger, Rails, Magician, and FlashyID. L
 4. 🧭 [Magician Trust](docs/guides/magician-routing.md) (5 min) — Trust graphs and routing
 5. 🔐 [FlashyID Assertions](docs/guides/flashyid-oauth.md) (5 min) — Verified assertions and delegation chains
 
-**Then run the [working examples](https://github.com/flashylabs/flashy-examples):**
+**Then run the [working examples](https://github.com/AgenteLabs/flashy-examples):**
 ```bash
 npm install && npm run examples:ledger
 npm run examples:rails
@@ -80,7 +80,7 @@ All four systems work together — FlashyID signs the assertion and the consent,
 
 ## Running the Examples
 
-All concepts are taught through runnable examples in [flashy-examples](https://github.com/flashylabs/flashy-examples):
+All concepts are taught through runnable examples in [flashy-examples](https://github.com/AgenteLabs/flashy-examples):
 
 ```bash
 npm run examples:ledger           # Ledger basics
@@ -121,7 +121,7 @@ npm test                          # All tests
 └── .github/workflows/        # doc-checks.yml runs both checkers; secret-scan.yml
 ```
 
-Worked examples live in the separate [flashy-examples](https://github.com/flashylabs/flashy-examples) repository.
+Worked examples live in the separate [flashy-examples](https://github.com/AgenteLabs/flashy-examples) repository.
 
 ## Contributing
 
@@ -141,8 +141,8 @@ Apache-2.0. Holder: Flashy Labs.
 ---
 
 **Quick Links:**
-- [Ledger Repo](https://github.com/flashylabs/flashy-ledger)
-- [Rails Repo](https://github.com/flashylabs/flashy-rails)
-- [Magician Repo](https://github.com/flashylabs/magician)
-- [FlashyID Repo](https://github.com/flashylabs/flashyid)
-- [Examples Repo](https://github.com/flashylabs/flashy-examples)
+- [Ledger Repo](https://github.com/AgenteLabs/flashy-ledger)
+- [Rails Repo](https://github.com/AgenteLabs/flashy-rails)
+- [Magician Repo](https://github.com/AgenteLabs/magician)
+- [FlashyID Repo](https://github.com/AgenteLabs/flashyid)
+- [Examples Repo](https://github.com/AgenteLabs/flashy-examples)
diff --git a/docs/INTEGRATOR-PROGRAM.md b/docs/INTEGRATOR-PROGRAM.md
@@ -170,7 +170,7 @@ For mission-critical integrations and long-term partnerships.
 
 ### Community Tier
 
-Send an issue to [flashy-examples](https://github.com/flashylabs/flashy-examples/issues/new) with:
+Send an issue to [flashy-examples](https://github.com/AgenteLabs/flashy-examples/issues/new) with:
 
 ```markdown
 # [INTEGRATOR] Your Company Name
@@ -322,8 +322,8 @@ A: Community (1 week), Standard (2 weeks), Strategic (4 weeks).
 ## Questions?
 
 - **Integrations:** [partnerships@flashylabs.com](mailto:partnerships@flashylabs.com)
-- **Technical:** [GitHub Issues](https://github.com/flashylabs/flashy-examples/issues)
-- **Community:** [GitHub Discussions](https://github.com/flashylabs/flashy-examples/discussions)
+- **Technical:** [GitHub Issues](https://github.com/AgenteLabs/flashy-examples/issues)
+- **Community:** [GitHub Discussions](https://github.com/AgenteLabs/flashy-examples/discussions)
 
 ---
 

diff --git a/docs/OPERATIONAL-PRINCIPLES.md b/docs/OPERATIONAL-PRINCIPLES.md
@@ -258,5 +258,5 @@ Each principle is backed by real incidents (ours or others'). Each one is non-ne
 ## Next
 
 - Read [The House Rules](../README.md#-the-house-rules-enforced) for how these principles are enforced
-- See [Working Examples](https://github.com/flashylabs/flashy-examples) for code that embodies them
+- See [Working Examples](https://github.com/AgenteLabs/flashy-examples) for code that embodies them
 - File issues if you find a place where a principle is violated
diff --git a/docs/api/flashyid-api.md b/docs/api/flashyid-api.md
@@ -9,7 +9,7 @@ disagrees with this page, this page was measured and the guide was not.
 
 Measured against flashyid at `98adaf1` (branch `claude/dreamy-bell-2e5nq3`;
 `packages/sdk/package.json` declares `@flashyid/sdk` `0.2.0`). Repository:
-<https://github.com/FlashyLabs/flashyid> (private).
+<https://github.com/AgenteLabs/flashyid> (private).
 
 ## Where it comes from
 

diff --git a/docs/api/ledger-api.md b/docs/api/ledger-api.md
@@ -8,7 +8,7 @@ measured and the guide was not.
 
 Measured against flashy-ledger at `d2a9c82` (branch `claude/dreamy-bell-2e5nq3`;
 `package.json` declares `@flashylabs/ledger` `1.0.0`; the top `CHANGELOG.md`
-entry is `[Unreleased]`). Repository: <https://github.com/FlashyLabs/flashy-ledger>
+entry is `[Unreleased]`). Repository: <https://github.com/AgenteLabs/flashy-ledger>
 (public).
 
 ## Where it comes from

diff --git a/docs/api/magician-api.md b/docs/api/magician-api.md
@@ -9,7 +9,7 @@ measured and the guide was not.
 
 Measured against magician at `f5c4fda` (branch `claude/dreamy-bell-2e5nq3`;
 `packages/core/package.json` declares `@magician-network/core` `0.1.0`).
-Repository: <https://github.com/FlashyLabs/magician>.
+Repository: <https://github.com/AgenteLabs/magician>.
 
 ## Where it comes from
 

diff --git a/docs/api/rails-api.md b/docs/api/rails-api.md
@@ -9,7 +9,7 @@ not.
 
 Measured against flashy-rails at `1fff537` (branch `claude/dreamy-bell-2e5nq3`;
 `package.json` declares `@flashylabs/rails` `1.0.0`, `private: false`, no
-`publishConfig`). Repository: <https://github.com/FlashyLabs/flashy-rails>
+`publishConfig`). Repository: <https://github.com/AgenteLabs/flashy-rails>
 (private).
 
 ## Where it comes from

diff --git a/docs/deployment/patterns.md b/docs/deployment/patterns.md
@@ -309,6 +309,6 @@ echo ".env*" >> .gitignore
 
 - [Ledger API](../api/ledger-api.md) · [Rails API](../api/rails-api.md) · [Magician API](../api/magician-api.md) · [FlashyID API](../api/flashyid-api.md)
 - [Local setup](../guides/setup-local.md)
-- [Working examples](https://github.com/flashylabs/flashy-examples)
+- [Working examples](https://github.com/AgenteLabs/flashy-examples)
 
-**Questions?** File an issue in [flashy-docs](https://github.com/flashylabs/flashy-docs/issues) or [flashy-examples](https://github.com/flashylabs/flashy-examples/issues).
+**Questions?** File an issue in [flashy-docs](https://github.com/AgenteLabs/flashy-docs/issues) or [flashy-examples](https://github.com/AgenteLabs/flashy-examples/issues).
diff --git a/docs/guides/aao-governance-conformance.md b/docs/guides/aao-governance-conformance.md
@@ -6,7 +6,7 @@ Learn AAO (Agentic Autonomous Organization), the `@flashyos/aao` manifest format
 > sources are the AAO spec at [flashyos.com/aao](https://flashyos.com/aao), the
 > naming standard at [flashyos.com/standard](https://flashyos.com/standard), and
 > the `@flashyos/aao` package on npm (its source is `packages/aao` in
-> `FlashyLabs/flashyos`, a private repository). Where this guide and the canon
+> `AgenteLabs/flashyos`, a private repository). Where this guide and the canon
 > disagree, the canon wins.
 
 ## What Problem Does It Solve?
@@ -142,7 +142,7 @@ don't work for you:
 
 ## Validation in Code (Example 13)
 
-[Example 13 in flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/13-aao-validation)
+[Example 13 in flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/13-aao-validation)
 is a faithful, dependency-free model of the `@flashyos/aao` static checker —
 `validateCharter` runs the same rules against the `aao:"0.1"` manifest, and
 `conformance` answers the seven questions (the four static answered, the three
@@ -262,9 +262,9 @@ two files — no onboarding call.
 - **AAO Spec:** [flashyos.com/aao](https://flashyos.com/aao)
 - **Naming Standard:** [flashyos.com/standard](https://flashyos.com/standard)
 - **What an AAO Is:** [gda.group answer](https://gda.group/answers/what-is-an-ai-autonomous-organization/)
-- **Package:** `@flashyos/aao` on npm (`npm i @flashyos/aao`); the canonical source is `packages/aao` in `FlashyLabs/flashyos`, a private repository
+- **Package:** `@flashyos/aao` on npm (`npm i @flashyos/aao`); the canonical source is `packages/aao` in `AgenteLabs/flashyos`, a private repository
 - **A charter in production:** [flashyos.com/.well-known/flashyos-charter.json](https://flashyos.com/.well-known/flashyos-charter.json) — FlashyOS's own `flashyos.roles.json`, served where the conformance suite reads it (the repository that holds the file is private; the served charter is public)
-- **Working example:** [Example 13: AAO validation](https://github.com/flashylabs/flashy-examples/tree/main/examples/13-aao-validation)
+- **Working example:** [Example 13: AAO validation](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/13-aao-validation)
 
 ## Next Steps
 

diff --git a/docs/guides/combined-workflow.md b/docs/guides/combined-workflow.md
@@ -387,4 +387,4 @@ introduction record carries `person/` slugs, not the ledger ids.
 
 - [Deployment Patterns](../deployment/patterns.md) — how the four are deployed together
 - The API pages, each measured against source: [Ledger](../api/ledger-api.md), [Rails](../api/rails-api.md), [Magician](../api/magician-api.md), [FlashyID](../api/flashyid-api.md)
-- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/05-combined-workflow) run at these commits
+- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/05-combined-workflow) run at these commits
diff --git a/docs/guides/flashyid-oauth.md b/docs/guides/flashyid-oauth.md
@@ -349,4 +349,4 @@ and `railGrantFromChain` on an unsound or uncapped chain.
 
 - Read the [Combined Workflow](combined-workflow.md) to see a chain become a rail grant beside a sealed introduction
 - Read the [FlashyID API](../api/flashyid-api.md) for every export, measured against source; the provider's own `docs/rail-issuance.md`, `docs/rail-consent.md` and `docs/rail-grant.md` cover the token contracts
-- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/04-flashyid-oauth) run at these commits
+- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/04-flashyid-oauth) run at these commits
diff --git a/docs/guides/intentmesh-roadmaps.md b/docs/guides/intentmesh-roadmaps.md
@@ -306,12 +306,12 @@ IntentMesh is one of four standards:
 | **Witnessed Observances** | `ritual/1` | Verifiable reputation/standing (Rites) |
 | **Governance** | `aao/1` | Machine-readable authority (GDA-OS) |
 
-See [Example 11: IntentMesh Roadmaps](https://github.com/flashylabs/flashy-examples/tree/main/examples/11-intentmesh) for working code.
+See [Example 11: IntentMesh Roadmaps](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/11-intentmesh) for working code.
 
 ## Resources
 
-- **Full Spec:** [IntentMesh SPEC.md](https://github.com/FlashyLabs/intentmesh/blob/main/SPEC.md)
+- **Full Spec:** [IntentMesh SPEC.md](https://github.com/AgenteLabs/intentmesh/blob/main/SPEC.md)
 - **Adoption Guide:** `npx intentmesh --help`
-- **Reference Implementation:** [intentmesh CLI](https://github.com/FlashyLabs/intentmesh)
+- **Reference Implementation:** [intentmesh CLI](https://github.com/AgenteLabs/intentmesh)
 - **Live Example:** `https://flashygroup.com/.well-known/intent.json`
 
diff --git a/docs/guides/ledger-101.md b/docs/guides/ledger-101.md
@@ -350,4 +350,4 @@ try {
 
 - Learn [Rails Consent](rails-consent.md) — the layer that calls `post` on your behalf and gates every debit on the holder's consent
 - Read the [Ledger API](../api/ledger-api.md) for every export, measured against source
-- [Local setup](setup-local.md) — installing the package from a sibling checkout; note its §4 on which examples in [flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/01-ledger-basics) run at these commits
+- [Local setup](setup-local.md) — installing the package from a sibling checkout; note its §4 on which examples in [flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/01-ledger-basics) run at these commits
diff --git a/docs/guides/magician-routing.md b/docs/guides/magician-routing.md
@@ -321,4 +321,4 @@ if (routes.length === 0) {
 - Learn [FlashyID: Assertions and Delegated Authority](flashyid-oauth.md) — the identity seam `flashyIdProvider` binds to
 - Read the [Combined Workflow](combined-workflow.md) to see a sealed introduction lead into a consented Rails transfer
 - Read the [Magician API](../api/magician-api.md) for every export, measured against source
-- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/03-magician-intro) run at these commits
+- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/03-magician-intro) run at these commits
diff --git a/docs/guides/mesh-integration.md b/docs/guides/mesh-integration.md
@@ -6,7 +6,7 @@ that view honest. This is the *consumer* half of the standards; the producer
 half is each format's own guide.
 
 Working example:
-[Example 14: Mesh Reference Consumer](https://github.com/flashylabs/flashy-examples/tree/main/examples/14-mesh-consumer).
+[Example 14: Mesh Reference Consumer](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/14-mesh-consumer).
 
 ## The shape of a consumer
 

diff --git a/docs/guides/rails-consent.md b/docs/guides/rails-consent.md
@@ -366,4 +366,4 @@ try {
 - Learn [Magician Routing](magician-routing.md) — consent-gated introductions, the other place "agents suggest; humans consent" is enforced in code
 - Read [FlashyID: Assertions and Delegated Authority](flashyid-oauth.md) for who signs the consent and grant tokens
 - Read the [Rails API](../api/rails-api.md) for every export, measured against source
-- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/02-rails-consent) run at these commits
+- [Local setup](setup-local.md) §4 says which [flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/02-rails-consent) run at these commits
diff --git a/docs/guides/rites-witnessed-observances.md b/docs/guides/rites-witnessed-observances.md
@@ -5,7 +5,7 @@ recurring, witnessed, consequence-bearing act: a practice happening now, on a
 rhythm a stranger can check.
 
 > **Canon first.** The authoritative source is
-> [`Rites-Network/SPEC.md`](https://github.com/FlashyLabs/Rites-Network/blob/main/SPEC.md).
+> [`Rites-Network/SPEC.md`](https://github.com/AgenteLabs/Rites-Network/blob/main/SPEC.md).
 > Where this guide and the spec disagree, the spec wins.
 
 ## Three Tenses
@@ -88,7 +88,7 @@ observances performed against them.
       "for": "org/flashy-ledger",
       "at": "2026-10-09T11:23:02Z",
       "recorded": "2026-10-09T11:23:16Z",
-      "evidence": "https://github.com/FlashyLabs/flashy-ledger/actions/runs/37923379270",
+      "evidence": "https://github.com/AgenteLabs/flashy-ledger/actions/runs/37923379270",
       "state": "witnessed",
       "witness": {
         "by": "org/gda-capital",
@@ -103,7 +103,7 @@ observances performed against them.
 The `evidence` above is a real run of flashy-ledger's `shiplog.yml` workflow
 — the public repository's own refresh of its `shipped/1` log — and it is the
 kind of URL the rule asks for: one a stranger can open. An earlier version of
-this sample cited a run in `FlashyLabs/flashyos`, which is a private
+this sample cited a run in `AgenteLabs/flashyos`, which is a private
 repository; a stranger following that link gets a 404, so it would have failed
 the format's own evidence rule.
 
@@ -174,7 +174,7 @@ is anchored to a party that answers separately.
 ## Metrics, the Anti-Metric, and the Projection
 
 Standing must be legible without being gameable. Two functions carry that, and
-[Example 12 in flashy-examples](https://github.com/flashylabs/flashy-examples/tree/main/examples/12-rites)
+[Example 12 in flashy-examples](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/12-rites)
 implements both.
 
 **Metrics ship the witnessed share with the raw count.** `metrics()` returns
@@ -224,7 +224,7 @@ is an observance climbing the ladder:
   "for": "org/ritualos",
   "at": "2026-09-01T04:00:00Z",
   "recorded": "2026-09-01T04:00:05Z",
-  "evidence": "https://github.com/FlashyLabs/ritualos/actions/runs/9001",
+  "evidence": "https://github.com/AgenteLabs/ritualos/actions/runs/9001",
   "state": "performed"
 }
 ```
@@ -260,8 +260,8 @@ They compose:
 
 ## Resources
 
-- **Spec:** [`Rites-Network/SPEC.md`](https://github.com/FlashyLabs/Rites-Network/blob/main/SPEC.md)
-- **Working example:** [Example 12: ritual/1](https://github.com/flashylabs/flashy-examples/tree/main/examples/12-rites)
+- **Spec:** [`Rites-Network/SPEC.md`](https://github.com/AgenteLabs/Rites-Network/blob/main/SPEC.md)
+- **Working example:** [Example 12: ritual/1](https://github.com/AgenteLabs/flashy-examples/tree/main/examples/12-rites)
 - **The three tenses:** `docs/tenses.md` in the estate
 - **Sibling formats:** `backlog/1` (future), `shipped/1` (past)
 

diff --git a/docs/guides/setup-local.md b/docs/guides/setup-local.md
@@ -41,12 +41,12 @@ file:../flashy-ledger …`), which is the path below.
 
 ```bash
 mkdir flashy && cd flashy
-git clone https://github.com/FlashyLabs/flashy-ledger
-git clone https://github.com/FlashyLabs/flashy-rails
-git clone https://github.com/FlashyLabs/magician
-git clone https://github.com/FlashyLabs/flashyid
-git clone https://github.com/FlashyLabs/flashy-examples
-git clone https://github.com/flashylabs/flashy-docs
+git clone https://github.com/AgenteLabs/flashy-ledger
+git clone https://github.com/AgenteLabs/flashy-rails
+git clone https://github.com/AgenteLabs/magician
+git clone https://github.com/AgenteLabs/flashyid
+git clone https://github.com/AgenteLabs/flashy-examples
+git clone https://github.com/AgenteLabs/flashy-docs
 ```
 
 Before reading anything as "what ships", ask each checkout which branch is its

diff --git a/flashyos.roles.json b/flashyos.roles.json
@@ -9,7 +9,7 @@
   "repositories": [
     {
       "name": "flashy-docs",
-      "url": "github.com/FlashyLabs/flashy-docs",
+      "url": "github.com/AgenteLabs/flashy-docs",
       "default": true,
       "holds": [
         "library",