Org rule: every app-influencing parameter is read from the database (with an ESLint guard) — all products
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 12/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- eslint, java, typescript
- Domain
- database, developer-experience, documentation, tooling
Research direction
This is a cross-repository policy rollout, not a single-file change. Start with the AGENTS.md and org template files that should receive the rule, then the @krizaka/config package where krizakaStack() would hold a new ESLint rule and the lint-ratchet.json baseline. Done means the rule text lands in each product, the guard refuses unmarked numeric exports under src/<feature>/**, and the baseline is recorded; the settings module design and the Orochia rollout (orochia#205) need maintainer input first.
Written by the indexing model from the issue text.
Description
Rule decided 2026-10-15 (Oussama): any parameter that influences the application's behaviour (amounts, thresholds, durations, limits, quotas, percentages, ladders, policy texts, feature flags) is read from the database — static but changeable: versioned settings per domain, seed = version 1, coded safety bounds, admin page (draft → preview → publish with reason → audit log → rollback), cache invalidated on publish, long-lived objects snapshot the version they were created under.
Only exceptions, each marked // @fixed: <reason>: (1) what must be known before the DB can be read or differs per deployment → env var (lib/env); (2) technical facts imposed by a technology/model and pure UI tuning → code constant. Decision test: could a business owner or operator want to change it without a redeploy? yes ⇒ DB.
Do: (a) add the rule to every product's AGENTS.md and to the org template; (b) an ESLint rule in @krizaka/config (krizakaStack()) that refuses a numeric/duration export const under src/<feature>/** without // @fixed:; ratchet the existing count down (lint-ratchet.json); (c) a shared settings module pattern (TS: @krizaka/settings facade over the product's DB; Java: a krizaka-platform-kit settings starter) so each product doesn't reinvent versioning/audit/cache; (d) apply first in Orochia (orochia#205), then Orazaka (spend guards, quotas, pricing are already partly env — move the business ones), Yomizaka, Kachizaka (already sealed rule sets), Akinaza (tax rates by date), Yasakia.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 52m
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from krizaka/.github
-
area:growth owner:oussama priority:later product:krizaka product:site type:design
Difficulty 1/5 Under an hour Newbie friendliness 68/100
krizaka/.github#15 · 2 comments ·
Maintainers usually reply within 1 day
-
area:architecture area:backend priority:next product:krizaka type:feature
Difficulty 5/5 Over a week Newbie friendliness 12/100
krizaka/.github#67 · 1 comment ·
Maintainers usually reply within 1 day
-
area:architecture area:compliance priority:next product:krizaka type:feature
Difficulty 5/5 Over a week Newbie friendliness 8/100
krizaka/.github#66 · 1 comment ·
Maintainers usually reply within 1 day
-
area:architecture area:infra priority:next product:krizaka type:feature
Difficulty 5/5 Over a week Newbie friendliness 15/100
krizaka/.github#65 · 1 comment ·
Maintainers usually reply within 1 day
-
priority:next
Difficulty 5/5 Over a week Newbie friendliness 8/100
krizaka/.github#64 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:session-state issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openclaw/wacli#503 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
area:casework criticality:p3
Difficulty 1/5 Under an hour Newbie friendliness 94/100
registrystack/registry-stack#2084 ·
Maintainers usually reply within 1 day
-
area/indexing bug package/core triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Add: AVA MediaOpenchannels:add check:failed
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day