Luigit
repositories / dotfiles

dotfiles

bugabingas dorkfiles

owned by admin

quickshell/nuguland/.system/phases/NL-PHASE-NHO6XZIJ-architecture-revamp/index.md

Raw
Rendered preview

id: NL-PHASE-NHO6XZIJ type: phase title: Architecture revamp label: arch-revamp

Architecture revamp

Sub-mission: make public-contract onboarding the default mode of change in Nuguland. Governing contract NL-SPEC-A7K4QX2M; rollout NL-PLAN-C4V7TQ2X.

Priorities

  1. Locality: one registration site, feature-local slices.
  2. Proof rigor: zero warnings, isolated nested evidence, reviewed pixels.
  3. Owner judgement on recorded metrics over velocity.
  4. Minimal churn per slice; no big-bang rewrite.

Decision defaults

Concern Default
Locality vs rigor Rigor wins
New features Registry contract from day one
Existing features Migrate slice-wise, one named fixture at a time
Activation Startup composition only
Internal state API JSON stays until the typed follow-up decides
Lock/auth Specialized controllers, never the popup lifecycle
Gates Never weakened to make an iteration green

Non-goals

Plugin ecosystem; user configuration; runtime activation; repository-wide rewrite.

Exit criteria

  • One registry entry plus feature-local files is the entire wiring for an ordinary feature.
  • OSD onboarded by a second agent from public contracts alone.
  • Owner continuation judgement recorded against baseline metrics.
  • All gates green throughout: lint, JS suite, ui-test.
---
id: NL-PHASE-NHO6XZIJ
type: phase
title: Architecture revamp
label: arch-revamp
---

# Architecture revamp

Sub-mission: make public-contract onboarding the default mode of change in Nuguland. Governing contract `NL-SPEC-A7K4QX2M`; rollout `NL-PLAN-C4V7TQ2X`.

## Priorities

1. Locality: one registration site, feature-local slices.
2. Proof rigor: zero warnings, isolated nested evidence, reviewed pixels.
3. Owner judgement on recorded metrics over velocity.
4. Minimal churn per slice; no big-bang rewrite.

## Decision defaults

| Concern | Default |
| --- | --- |
| Locality vs rigor | Rigor wins |
| New features | Registry contract from day one |
| Existing features | Migrate slice-wise, one named fixture at a time |
| Activation | Startup composition only |
| Internal state API | JSON stays until the typed follow-up decides |
| Lock/auth | Specialized controllers, never the popup lifecycle |
| Gates | Never weakened to make an iteration green |

## Non-goals

Plugin ecosystem; user configuration; runtime activation; repository-wide rewrite.

## Exit criteria

- [ ] One registry entry plus feature-local files is the entire wiring for an ordinary feature.
- [ ] OSD onboarded by a second agent from public contracts alone.
- [ ] Owner continuation judgement recorded against baseline metrics.
- [ ] All gates green throughout: lint, JS suite, ui-test.