First siax manifest for this repo (none existed). Schema-validated against
siax-standard's siax.repo.v3.schema.json and siax.repo.schema.json (both
valid:true, zero errors), and siax-doctor's `repo` command confirms
REPO-16/REPO-03/REPO-04 all PASS.
Fields reflect the repo's actual current state, not aspiration:
- category: business, tier: satellite (adopted external AGPL-3.0-or-later
OSS product, upstream Jakob Wennberg/gnubok; not a SIAX-native platform
capability -- same pattern as crm-siax's Twenty CRM fork).
- operationalState: planned (imported into sax3l 2026-09-10, governance
scaffold only so far -- PLAN/MASTERPLAN_INDEX.md's X-120 is still at
SCAFFOLDED, no SIAX-operated deployment/domain/node exists yet).
- replacesSaaS: [Fortnox] per Simon's 2026-09-14 decision (ERPNext/Accounted,
not Fortnox).
- licenses.approved: false (AGPL-3.0-or-later has real network-copyleft
implications for a self-hosted operator; no compliance sign-off found).
- decoupled: true, as the v2 schema's business-category rule requires and
as this repo's actual architecture is (no @siax/* deps, consumes: []).
- appId: null with a written justification (no CL0UD APP_REGISTRY entry).
Pure addition: two new root-level JSON files, nothing else touched.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
adminandClaude Sonnet 5