[SPEC] Developer standards — modular purity, local-first, SOUL compliance #7

New Issue

perplexity · 2026-03-27T22:48:31Z

perplexity commented

2026-03-27 22:48:31 +00:00

Source

Sovereign Developer's Brief (2026-03-27), Section 3 "Developer Standards & Philosophy".

What

Create specs/developer-standards.md codifying the four principles from the brief as enforceable rules:

Principle	Rule
Modular Purity	No file exceeds 1,000 lines. Refactor into modules.
No Main Pushes	Direct pushes to `main` forbidden. PRs for every change.
Local-First	Every API-dependent feature must have a local fallback or a clear path to local hosting.
SOUL.md Compliance	All agent behaviors grounded in the Prime Directive (Brevity, Honesty, Directness).

Why

These rules are stated in the brief but not yet tracked in a repo-level spec. Codifying them makes them enforceable by PR review automation.

Acceptance

specs/developer-standards.md exists with the four rules, rationale, and examples of violations
Cross-referenced from both timmy-config/README.md and timmy-home/README.md

## Source Sovereign Developer's Brief (2026-03-27), Section 3 "Developer Standards & Philosophy". ## What Create `specs/developer-standards.md` codifying the four principles from the brief as enforceable rules: | Principle | Rule | |---|---| | Modular Purity | No file exceeds 1,000 lines. Refactor into modules. | | No Main Pushes | Direct pushes to `main` forbidden. PRs for every change. | | Local-First | Every API-dependent feature must have a local fallback or a clear path to local hosting. | | SOUL.md Compliance | All agent behaviors grounded in the Prime Directive (Brevity, Honesty, Directness). | ## Why These rules are stated in the brief but not yet tracked in a repo-level spec. Codifying them makes them enforceable by PR review automation. ## Acceptance - `specs/developer-standards.md` exists with the four rules, rationale, and examples of violations - Cross-referenced from both `timmy-config/README.md` and `timmy-home/README.md`

Timmy was assigned by Rockachopa

2026-03-28 03:52:32 +00:00

Timmy referenced this issue

2026-03-28 04:45:34 +00:00

[SPEC] Developer standards — modular purity, local-first, SOUL compliance #8

Timmy commented

2026-03-28 04:55:20 +00:00

Closing during the 2026-03-28 backlog burn-down.

Reason: this is a broad legacy frontier. The work, if still valuable, will return as narrower final-vision issues after reset with direct proof-oriented acceptance criteria.

Closing during the 2026-03-28 backlog burn-down. Reason: this is a broad legacy frontier. The work, if still valuable, will return as narrower final-vision issues after reset with direct proof-oriented acceptance criteria.

Timmy closed this issue

2026-03-28 04:55:20 +00:00

Timmy referenced this issue

2026-03-31 16:59:45 +00:00

[STUDY] JSONL session storage — crash-safe append-only writes #168

allegro referenced this issue

2026-04-01 06:31:13 +00:00

🔥 Burn Report #7 — 2026-04-01 — AdaptiveCalibrator + Alembic E2E + Crisis Safety #218

ezra referenced this issue

2026-04-04 16:09:47 +00:00

[GRAND EPIC] Alexander's Vision — Unified Fleet Assessment & Priority Stack (1,031 Issues Audited) #387

Timmy referenced this issue