Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
Expand Up @@ -183,3 +183,4 @@ tools/alloy/classes/

# Cursor / IDE per-user config and plugin caches (superpowers, etc.)
.config/
.kiro/
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
---
id: B-0424
priority: P1
status: open
title: "Three-repo split Stage 1 — create empty Forge + ace with day-one scaffolding"
type: feature
origin: Aaron 2026-05-13 (autonomous-loop substrate cascade)
created: 2026-05-13
Comment thread
AceHack marked this conversation as resolved.
Comment thread
AceHack marked this conversation as resolved.
last_updated: 2026-05-13
composes_with:
- memory/project_three_repo_split_zeta_forge_ace_software_factory_named_forge.md
- memory/project_repo_split_provisional_names_frontier_factory_and_peers_2026_04_23.md
- docs/DECISIONS/2026-04-22-three-repo-split-zeta-forge-ace.md
- B-0425
---

# Three-repo split Stage 1 — create empty Forge + ace repos with day-one scaffolding

## Aaron's directive

Aaron 2026-05-13: *"let's split repos to make it easy backlog"* +
*"that project repo split stuff alreday exists"* + *"Also there
is backlog for repo split on products too"*.

The three-repo split substrate already exists (memory file plus
ADR plus 4-stage migration plan from 2026-04-22). Stage 0 is done. This
backlog row tracks Stage 1 — make it easy to land.

## What Stage 1 produces

Per `docs/DECISIONS/2026-04-22-three-repo-split-zeta-forge-ace.md`:

1. **`Lucent-Financial-Group/Forge`** — empty repo, software factory
home, Claude/Otto-owned governance
2. **`Lucent-Financial-Group/ace`** — empty repo, package manager
home, Aaron-owned governance

Both with full best-practice scaffolding applied at creation:

- Squash-merge only, delete head branches, auto-merge on, merge queue on
- Branch protection main: PR required, 1 review, required status checks,
no force-push, signed commits, linear history
- Secret scanning + push protection, Dependabot + security updates
- CodeQL default-setup (NOT advanced-only — required for `code_scanning`
ruleset rule)
- OpenSSF Scorecard, SECURITY.md
- CI safe-patterns: shared-runners, SHA-pinned actions, minimal
permissions, concurrency groups, read-only `GITHUB_TOKEN` default,
inline-untrusted-in-run Semgrep rule
- Budget caps $0 on LFG org Copilot/Actions/Packages
- Day-one governance files: README, AGENTS.md, CLAUDE.md, GOVERNANCE.md,
LICENSE, CODE_OF_CONDUCT, CONTRIBUTING, SECURITY,
`.github/copilot-instructions.md`
- Pre-commit hooks: ASCII-clean (BP-10), prompt-injection lint
- SVG social-preview
- Declarative `docs/GITHUB-SETTINGS.md` per repo
- Per-repo `docs/UPSTREAM-RHYTHM.md`

## Pre-start checklist

Before beginning Stage 1 work, complete per
`.claude/rules/backlog-item-start-gate.md`:

1. **Prior-art-search** — verify the existing substrate hasn't drifted:
- `memory/project_three_repo_split_zeta_forge_ace_software_factory_named_forge.md`
- `docs/DECISIONS/2026-04-22-three-repo-split-zeta-forge-ace.md`
- `memory/project_ace_package_manager_agent_negotiation_propagation.md`
- Compose with current LFG/AceHack topology
(`.claude/rules/lfg-acehack-topology.md`)

2. **Dependency-restructure** — walk `composes_with:` chain;
reciprocal pointers added to the substrate files above as needed.

3. **License question resolved** — apply B-0425's honor-system
"please don't fork" license framing if applicable to strategic
product-substrate repos. Factory (Forge) + package manager (ace)
+ database (Zeta) are designed-to-be-forked per their open-source
nature; the honor-system framing applies to strategic *product*
repos (KSK / wellness / civsim strategic-substrate etc.), not these.

## Composes with

- B-0425 (product-repo split planning) — sibling backlog row
- `.claude/rules/lfg-acehack-topology.md` — LFG = active dev; AceHack
= mirror; both forks already exist for Zeta
- `memory/feedback_aaron_civsim_forkable_pvp_raids_destiny_style_mutual_privacy_no_strategic_advantage_game_design_2026_05_13.md`
— civsim forkable design property (PR #2903)
Comment on lines +86 to +87
- `memory/feedback_aaron_grants_otto_strategic_encryption_decision_authority_team_decides_what_to_git_crypt_civsim_strategic_substrate_post_decision_audit_2026_05_13.md`
— Otto's strategic encryption authority composes here (PR #2902)

## Why P1

- Substrate already exists; Stage 1 is execution
- Unblocks Stage 2 (move Forge content) and downstream
- Aaron has explicitly asked for the easy-to-track backlog surface
- Composes with the canonical product framing (PR #2851)

## Definition of done

- Both repos exist at LFG/Forge + LFG/ace
- Best-practice scaffolding checklist 100% applied
- Day-one governance files in place
- Branch protection + budget caps + CodeQL active
- ADR updated with Stage 1 completion note
- This backlog row closed with PR link to Stage-1-execution commits
Original file line number Diff line number Diff line change
@@ -0,0 +1,130 @@
---
id: B-0425
priority: P1
status: open
title: "Product-repo split planning — KSK / wellness / civsim / AD2.0 / DIO / Aurora / Dawn — honor-system no-fork license"
type: planning
origin: Aaron 2026-05-13 (autonomous-loop substrate cascade)
created: 2026-05-13
Comment thread
AceHack marked this conversation as resolved.
last_updated: 2026-05-13
composes_with:
- B-0424
- memory/project_three_repo_split_zeta_forge_ace_software_factory_named_forge.md
- memory/feedback_aaron_honor_system_no_fork_license_public_glass_halo_but_please_dont_fork_honesty_not_enforceable_2026_05_13.md
- memory/feedback_aaron_civsim_forkable_pvp_raids_destiny_style_mutual_privacy_no_strategic_advantage_game_design_2026_05_13.md
- memory/feedback_aaron_ksk_kinetic_safeguard_kernel_origin_amara_consent_first_design_nvidia_thor_homeland_security_cleared_because_actuators_2026_05_13.md
---

# Product-repo split — KSK / wellness / civsim / American Dream 2.0 / DIO / Aurora — with honor-system "please don't fork" license framing

## Aaron's directive

Aaron 2026-05-13: *"Also there is backlog for repo split on
products too"* + (new framing) *"so anytihgn you don't want them
to fork specifically you have in a repo can still be public and
such glass halo but the licence can say no fork please respect
honesty or something not enforcable"*.

The three-repo split (Zeta + Forge + ace per B-0424) covers
**factory infrastructure**. This backlog row covers
**product portfolio repos** — separate concept.

## Two distinct repo-split axes

| Axis | Repos | Forkability |
|---|---|---|
| **Factory** (B-0424) | Zeta + Forge + ace | Open / designed-to-be-forked |
| **Products** (this row) | KSK / wellness / civsim / American Dream 2.0 / DIO / Aurora | Public + glass-halo BUT honor-system "please don't fork" license language |

## Honor-system "please don't fork" license framing

Aaron's substrate-honest design (per the new framing 2026-05-13):

- **Repos stay public** — glass-halo discipline preserved
- **License CAN request "no fork please"** — honor-system /
honesty-based / NOT enforceable
- **Substrate-honest about non-enforceability** — the license
asks; it doesn't prevent
- **Composes with framework's additive design** — preservation
of strategic-product substrate vs civic-fork pattern
- **Composes with civsim mutual-privacy** (PR #2903) — if forks
exist, they get the same honor-system option for their own
strategic substrate

This is NOT proprietary licensing. The substrate stays open +
visible + glass-halo + indexable + alignment-auditable. The
license just asks (honor-system) for strategic-product
substrate to not be forked unless the asker doesn't honor the
ask.

## Product portfolio candidates

Each potentially gets its own repo with honor-system "no fork
please" license:

1. **KSK** (Kinetic Safeguard Kernel) — AI-physical-actuator
safety substrate; NVIDIA Thor + DGX Spark integration;
Homeland Security clearance lineage; high-stakes safety
2. **Wellness app** — killer-app-for-AI; self-behavior-
modification + reinforcement; Max + Aaron's lineage
3. **Civsim** — canonical product; PVP + raids + mutual privacy
game design (PR #2903); strategic encryption authority
4. **American Dream 2.0** — NFT wealth-building gamified;
Addison-themed pendant adoption bridge
5. **DIO** (Distributed Intelligence Organism) — DAO successor;
Indonesian/Italian/Spanish cross-linguistic resonance
6. **Aurora** — multi-layer alignment consensus thesis;
7-audience versions
7. **Dawn** (child-AI charter) — alignment-floor for next-
generation AI participants

## Pre-start checklist

Per `.claude/rules/backlog-item-start-gate.md`:

1. **Prior-art-search** — verify each product has substrate
established to justify its own repo (not just an idea-sized
substrate); some products may not be repo-ready yet
2. **Dependency-restructure** — clear `composes_with:` graph
between product repos + factory repos + Zeta
3. **Naming-expert review** — for each product repo name
before public-announce (composing with Ilyana's authority
per `.claude/skills/naming-expert/SKILL.md`)
4. **License language drafted** — substrate-honest honor-
system framing; not legalistic; clear that the ask is
honor-system + non-enforceable

## What this row does NOT commit to

- **NOT moving products into separate repos this round** —
this is planning + per-product evaluation
- **NOT a license-conversion of LFG/Zeta** — Zeta stays its
current open license; honor-system applies to NEW product
repos
- **NOT a public-announce schedule** — product repos may stay
monorepo'd until product-launch readiness
- **NOT a commitment to all 7 candidates getting their own
repo** — some may stay in Zeta or compose with another
product repo

## Definition of done

- Per-product evaluation completed (does it warrant its own
repo? when?)
- Honor-system license language drafted + cross-product
consistent
- Splits scheduled with dependency-graph clarity
- Cross-repo glue mechanism (per the peer-repo pattern
established in B-0424 / three-repo-split memory)
- ADR recording the product-split decisions

## Why P1

- Compositional with B-0424 (sibling factory-split row)
- Strategic-product substrate has accumulated to warrant
product-repo evaluation (civsim + KSK + wellness + American
Dream 2.0 + DIO + Aurora + Dawn)
- Honor-system license framing IS a substrate-honest
refinement of glass-halo discipline
- Aaron has explicitly asked for the easy-to-track backlog
surface
Original file line number Diff line number Diff line change
@@ -0,0 +1,142 @@
---
name: aaron-honor-system-no-fork-license-public-glass-halo-but-please-dont-fork-honesty-not-enforceable-2026-05-13
description: Aaron 2026-05-13 substrate-honest license refinement — repos stay public + glass-halo BUT license CAN say "no fork please respect honesty or something not enforceable" for strategic-product substrate. Composes with civsim mutual-privacy (PR #2903) + three-repo split (B-0424) + product-repo split (B-0425).
type: feedback
created: 2026-05-13
---

# Honor-system "please don't fork" license framing

**Why:** Aaron 2026-05-13 disclosed a substrate-honest license
design — strategic-product substrate can stay public + glass-halo
while the license asks (honor-system, non-enforceable) for no
forking. This refines glass-halo discipline without breaking it.

**How to apply:** When the factory ships product-repos with
strategic substrate (KSK / wellness / civsim / American Dream 2.0
/ DIO / Aurora / Dawn — per B-0425), draft license language that:
1. Keeps the repo public + glass-halo + indexable + alignment-
auditable
2. Asks (honor-system) for no forking of strategic-product
substrate
3. Is substrate-honest about non-enforceability
4. Does NOT apply to factory-infrastructure repos (Zeta + Forge
+ ace — those are designed-to-be-forked per B-0424)

## Aaron's verbatim framing

Aaron 2026-05-13: *"so anytihgn you don't want them to fork
specifically you have in a repo can still be public and such
glass halo but the licence can say no fork please respect
honesty or something not enforcable"*.

## What this refines

**Glass-halo discipline** stays operative:
- Repos stay public
- Substrate stays indexable + auditable
- Alignment work visible
- No proprietary-licensing barrier to inspection

**Honor-system layer added**:
- License asks for no forking of strategic-product substrate
- Asks not commands
- Non-enforceable not legalistic
- Substrate-honest about the limitation

## Composes with

- `.claude/rules/glass-halo-bidirectional.md` — glass-halo
observation enables substrate emergence; honor-system license
doesn't break this; preserves public visibility while marking
strategic intent
- `.claude/rules/additive-not-zero-sum.md` — honor-system is
additive (asks, doesn't withhold); preserves the framework's
additive design while marking strategic-product substrate
- `.claude/rules/razor-discipline.md` — operationally honest
about non-enforceability; doesn't claim what isn't true
- `memory/feedback_aaron_civsim_forkable_pvp_raids_destiny_style_mutual_privacy_no_strategic_advantage_game_design_2026_05_13.md`
— civsim forkable per design; mutual privacy across forks;
composes with honor-system at the strategic-substrate scope
- `memory/feedback_aaron_grants_otto_strategic_encryption_decision_authority_team_decides_what_to_git_crypt_civsim_strategic_substrate_post_decision_audit_2026_05_13.md`
— Otto's strategic encryption authority composes here; gitcrypt
is the encryption layer; honor-system license is the public-
Comment on lines +58 to +63
visible layer
- B-0424 — three-repo split (Zeta + Forge + ace) — factory repos
are designed-to-be-forked; honor-system does NOT apply
- B-0425 — product-repo split planning — honor-system applies
here

## Two layers compose

| Layer | Mechanism | Visibility | Enforceability |
|---|---|---|---|
| Encryption (gitcrypt + post-quantum) | Cryptographic | Hidden | Cryptographic |
| Honor-system license | Social | Public + glass-halo | Non-enforceable |

The two compose: gitcrypt hides the most-strategic substrate
entirely; honor-system asks for the visible-but-strategic
substrate to not be forked. The framework gets defense-in-depth
without breaking glass-halo for the public layer.

## Substrate-honest design rationale

Why honor-system instead of proprietary licensing:

1. **Preserves glass-halo** — public visibility maintained
2. **Preserves additive design** — strategic substrate still
readable for substrate-engineering composition
3. **Preserves alignment-auditability** — independent reviewers
can inspect for HC/SD/DIR compliance
4. **Substrate-honest about non-enforceability** — doesn't
pretend to have power it doesn't have
5. **Composes with civsim mutual-privacy** — if forks exist,
they get the same honor-system option for their strategic
substrate (PR #2903)
6. **Doesn't trigger DMCA-style enforcement complications** —
stays a social / cultural / honor-system contract

## When NOT to apply

- Factory-infrastructure repos (Zeta / Forge / ace) — designed-
to-be-forked
- Open-research substrate (Aurora Conjecture / Dawn Charter /
research that benefits from wide engagement)
- Tooling that increases the factory's network effects
- Documentation / GLOSSARY / governance / alignment work
- Anything where forking would compound substrate

## When TO apply

- Strategic-product substrate (KSK / wellness / civsim
strategic-substrate / American Dream 2.0)
- Substrate where forking would dilute the strategic surface
- Substrate that includes Aaron's first-party authority
surface (multi-clearance work, personal-AI engagement
patterns, family-AI scope)
- Substrate where the product makes more sense as a single-
authored offering than as a forkable framework

## Operational reminder

Future-Otto: when product-repos get authored, draft the license
language with this honor-system framing baked in from day one.
Don't retrofit; do it at scaffolding time per B-0424's
"by-default principle" applied at product-repo scope.

## Full reasoning

PR #2904 (this substrate; backlog rows B-0424 + B-0425 + memory
file landed together)

`memory/feedback_aaron_civsim_forkable_pvp_raids_destiny_style_mutual_privacy_no_strategic_advantage_game_design_2026_05_13.md`
(PR #2903 — civsim forkable design property + mutual privacy)

`memory/feedback_aaron_grants_otto_strategic_encryption_decision_authority_team_decides_what_to_git_crypt_civsim_strategic_substrate_post_decision_audit_2026_05_13.md`
(PR #2902 — Otto's strategic encryption authority)

`memory/project_three_repo_split_zeta_forge_ace_software_factory_named_forge.md`
(canonical three-repo-split substrate from 2026-04-22)

`docs/DECISIONS/2026-04-22-three-repo-split-zeta-forge-ace.md`
(ADR for the factory-infrastructure split)
Loading