jsip.uk/ground

One place for the judgement the job produces.

Accounts, notes and practice in a single private store. It runs in your browser, encrypts itself at rest, works with no signal, and never sends anything anywhere.

01

Why it exists

This started as an audit of everything on this site, plus the installed skills and the reports written about the job itself. The same shape turned up in all of them.

A roadmap written, and none of it built The Future SE Stack ranks 22 systems by leverage and names five as buildable now. None existed. All five depend on the same missing thing: a store of judgement to draw from.
A complete operating model with nowhere to live Champion Deposits has a source framework, 25 topic tags, a contact schema, confidence scoring and frequency rules. Its README said plainly: The spreadsheet doesn't exist yet.
Five versions of one skill, each hand maintained inbox-sweep through inbox-sweep-v5. Every new sender meant a fresh copy of the whole map. Knowledge that belonged in data was sitting in prompt text.
A tracker designed so nothing accumulates The POV tracker gives each plan a unique storageKey so progress never collides. Correct for progress. It also sealed off sixty scenarios of hard-won knowledge the day each POV ended.
Research that started from zero every time The positioning skill re-researched, re-verified and re-derived on every run. Nothing it established on Monday was available to it on Friday.

Sixteen good things, none of which held anything up for the next one. The gap was not another app. It was the layer underneath.

Two things made it worth building rather than merely noting. First, every commercial equivalent (Vivun, Tribble, SiftHub, AutoRFP, Consensus) is cloud software bought by an employer, so the expertise accrues to their tenant and does not leave with you. Second, there were already two piano practice apps on this site and nothing at all for the skill that pays the mortgage.

02

What it is

Three ways into one store. They exist separately because they answer different questions at different moments, not because they hold different data.

Account shaped

Accounts

People and where they stand, what is still open, and above all what you promised and have not sent. One button gives you a brief you can read in a car park.

When: before the call

Topic shaped

Notes

The things that belong to no account: a limitation found in a lab, a proof point you can reuse anywhere, a competitor line heard first hand. Searchable by topic.

When: after the call

Skill shaped

Practice

Ninety-second reps on real questions under a clock. Mark yourself on clarity, evidence and control; the ones you fumble come back sooner. 44 vendor-neutral cards to start.

When: dead time

Today

The only screen you have to open. Overdue promises first, then accounts going quiet, then one line each for cards due and notes worth seeing again. One search box reaches accounts, people, threads, log entries, notes and kept answers.

03

How it holds together

Logging a meeting asks for five lines, and only five. The transcript already holds the record, so this is only for the part no recording can produce.

SO WHAT     What actually changed. "Nothing changed" is a valid answer.
THEY SAID   One quote. Verbatim, in their words.
I LEARNED   One thing you know now that you did not at 9am.
STILL OPEN  What is unresolved or still against you.
I OWE       What you promised, to whom, by when.

I owe becomes a promise with a date, so it can go overdue and find you. Still open becomes a tracked thread. I learned appears in Notes. Everything else follows from two rules.

Learnings are derived, not copied

An I learned line written against an account is never duplicated into Notes. The Notes view unions real notes with ones projected from log entries, so there is exactly one copy of the text.

Edit it on the account and the note changes with it. No sync step, no dedupe, and nothing that can quietly drift out of date.

A note is not a thread

A note records something observed and is true forever. A thread is something open that must be closed, and it drives the overdue logic. So notes surface on an account read-only, and promoting one into a tracked thread is a deliberate click.

Converting automatically would create two sources of truth for "is this still open", and slowly fill the brief with stale items nobody ever closed. The brief is the one screen that has to stay trustworthy.

One click between the three

Any objection, on a thread or a note, becomes a practice card. Any note that mentions an account can be promoted to a tracked thread. No exports, no imports, no files.

This is what merging three apps into one actually bought. Before, moving one sentence between them meant downloading a file and uploading it again.

04

The loop

00 The meeting happensTeams or Zoom writes the record. You write nothing during it.
01 Five lines, ninety secondsStraight afterwards. Promises get a date, open items get tracked.
02 What generalises moves outThe learning leaves the account and becomes something about the job.
03 What caught you out gets rehearsedThe objection becomes a card, and comes back until it stops catching you out.
04 The next call starts informedThe brief leads with what you promised and have not sent.

05

What it will not do

Worth knowing before you rely on it.

×

There is no recovery. The passphrase is never stored, so forgetting it means the data is gone. Put it in a password manager the moment you set it.

×

It does not sync. Each browser holds its own store. Moving between devices means an encrypted backup file, deliberately, because a sync service is a place your notes could live that is not yours.

×

Encryption is not magic. It protects the data at rest from someone opening the page on your unlocked machine. It cannot help against someone holding both the device and the passphrase.

×

Context packs are plaintext. That is their job, and they name real people. Paste them somewhere you would be comfortable sending the underlying notes.

×

Nothing is connected. No Gmail, no calendar, no CRM. The moment it depends on a connector, it belongs to whoever owns the connector.

Ready when you are

It asks for a passphrase on first open, and it is useful from the first rep.