Skip to content

feat: Configurable decisions archival thresholds in config.json #34

@diberry

Description

@diberry

Problem

Archival thresholds are hardcoded constants in nap.ts (20KB, 30 days). Different projects have different write rates. Active projects need lower thresholds; stable projects can tolerate higher ones.

From

Flight + EECOM reviews of #20 (solution A5).

Proposed Schema

{
  "decisions": {
    "maxSizeKB": 15,
    "archiveAfterDays": 30,
    "archiveImplementedAfterDays": 7,
    "autoArchiveImplemented": true,
    "maxEntries": 75,
    "warnAtSizeKB": 10
  }
}

nap.ts reads from config.json, falls back to current hardcoded defaults.

Owner

EECOM (Core Dev)

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestgo:needs-researchNeeds investigationsquadSquad triage inbox — Lead will assign to a membersquad:archiveResolved by upstream or no longer applicablesquad:flightAssigned to Flight (Lead)

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions