jacobh2/kvitt
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

SPEC v0.35: card purchases via Enable Banking (D-158 to D-176), plans K0 to K3

Browse Source 
Owner request and answers of 2026-10-24: each user connects their own SJ Prio
Mastercard through Enable Banking (restricted production, BankID); only the
card holder sees the purchases; a fourth bottom destination "Kortköp"
(revises D-048); "Anslut kort" in Settings with the card artwork; one- and
two-tap linking to household expenses; web as a later plan.

FR-22, §9.12 (CP-1 to CP-14), server schema 4 (migration 0004), Room 2,
E-36 to E-44, S-23 to S-27, W-21 to W-23, OQ-7, OQ-8. PLAN-K0 describes the
test app of 2ce317f and the remaining run and report; K1 server, K2 Android,
K3 web. HANDOFF and prompts/README updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Jacob Hagstedt
2026-10-24 11:39:19 +02:00
parent 2ce317f72c
commit b5114adc06
12 changed files with 885 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
prompts/K0.md
+25
View File
@@ -0,0 +1,25 @@
# Start prompt: K0 Card purchases spike (local Enable Banking test app)
You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/kvitt`), plan K0: card purchases spike. You have no context other than this prompt and the files it names.
Read PLAN-K0.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both (§9.12 is the card-purchase rules, FR-22 the acceptance criteria). The test app exists (`docs/spikes/k0/app.py`, `2ce317f`); your work is running it with the owner and writing the report.
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
- Next free decision id: {{NEXT_DECISION}}
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
- Schema version for any schema change: {{SCHEMA_VERSION}}
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
Orchestrator notes for this run:
{{ORCHESTRATOR_NOTES}}
Essentials (the plan has the detail):
- First step: from the main checkout, `git worktree add .claude/worktrees/agent-k0 -b agent-k0 main`; work only there, on branch `agent-k0`; `git reset --hard main`. Copy `docs/spikes/k0/.local/` from the main checkout if the owner's key is there (never commit it).
- Edit only `docs/spikes/k0/**` and `docs/spikes/K0-enable-banking.md`; anything else is a request to the orchestrator.
- Real purchase data shows only on the owner's screen. Never print, log, commit or report it; read the state only through `analysis_text` (PLAN-K0 §6 step 4). The application id stays out of every committed file.
- The owner's steps (PLAN-K0 §8) go to the orchestrator, worded for relay, one at a time; you never sign in anywhere yourself.
- No gate: run the checks of PLAN-K0 §7 and report what you ran.
- Stop and ask when a step could expose the owner's data, when Enable Banking's terms or control panel differ from the plan, or when the spec is ambiguous in a way that changes a decision.
- Commit on your branch, `git rebase main`. Never merge, push or remove the worktree.
Report: end with the report described in PLAN-K0.md §10: branch, head commit hash, the checks run, one answer per K0 item with proposed SPEC v0.36 text, the owner steps with their yes/no, HUMAN steps outstanding (worded for relay), requests to the orchestrator, open questions with section numbers.