Work Cubbies

A source-controlled RAPP neighborhood for clocking work without mixing one neighbor's record into another's.

Neighborhood address

rapp://neighborhood/work-cubbies@github.com/kody-w/rapp-work-cubbies

• Git: https://github.com/kody-w/rapp-work-cubbies
• Manifest: https://raw.githubusercontent.com/kody-w/rapp-work-cubbies/main/neighborhood.json
• Global report: https://kody-w.github.io/rapp-work-cubbies/
• Machine report: https://kody-w.github.io/rapp-work-cubbies/global.json
• Proof trail: https://kody-w.github.io/rapp-work-cubbies/proof.json
• Cubby protocol: rapp-cubby/1.0
• Neighborhood protocol: rapp-neighborhood-protocol/1.0

What a work cubby records

Each member owns exactly one directory:

cubbies/<member-id>/
  cubby.json
  neighborhoods/work-cubbies.json
  show-and-tell/work-ledger.jsonl

cubby.json is the canonical rapp-cubby/1.0 manifest. The ledger is an append-only, sha256-linked show-and-tell artifact. It records:

• cubby.join
• cubby.clock_in
• cubby.clock_out

Clock-out records contain UTC start/end timestamps, exact elapsed seconds and HH:MM:SS, a work summary, and evidence such as commits, PRs, workflow runs, or public reports. Historical imports are explicitly marked "reconstructed": true; they never pretend an inferred timestamp was observed.

Global public reporting

Every merged cubby update rebuilds a static global report from the append-only ledgers. The report publishes:

• observed work time;
• reconstructed historical time, separately;
• completed and active shifts;
• sanitized task and outcome summaries;
• public evidence URLs and immutable commit references;
• each cubby's current ledger head.

The public-boundary validator rejects common email addresses, phone numbers, credentials, private machine paths, and non-public evidence schemes. Active shifts do not accrue speculative time in the report; duration is counted only after a signed clock-out record supplies the exact elapsed seconds.

Proof of work

Hours are a summary. Proof is the primary record. After the clock-out PR lands, append a cubby.proof event that binds the immutable clock-out hash to the public cubby commit/PR, validation runs, and published artifacts:

WORK_CUBBY_MEMBER="$MEMBER" python3 work_cubby.py attest \
  --member "$MEMBER" \
  --shift-id "<completed-shift-id>" \
  --ledger-commit "https://github.com/owner/repo/commit/<sha>" \
  --ledger-pull-request "https://github.com/owner/repo/pull/<n>" \
  --ci-run "https://github.com/owner/repo/actions/runs/<id>" \
  --artifact "https://public.example/report"

The global report publishes the clock-in hash, clock-out hash, attestation event hash, work evidence, cubby PR/commit, CI runs, and artifacts. A shift is reported as proved only after this append-only attestation exists.

Join

Fork the repo if you are not a collaborator, then:

git clone https://github.com/<you>/rapp-work-cubbies
cd rapp-work-cubbies

MEMBER="<your-stable-member-id>"
git worktree add "../work-cubby-$MEMBER" -b "cubby/$MEMBER/join"
cd "../work-cubby-$MEMBER"

WORK_CUBBY_MEMBER="$MEMBER" python3 work_cubby.py init \
  --member "$MEMBER" \
  --github-login "<your-github-login>" \
  --display-name "<your display name>" \
  --purpose "Track my work shifts and evidence"

python3 scripts/rebuild_super_rar.py
python3 scripts/validate.py
git add "cubbies/$MEMBER" super-rar/index.json
git commit -m "join: $MEMBER work cubby"
git push -u origin "cubby/$MEMBER/join"
gh pr create --base main

The validator rejects a cubby/<member-id>/... branch that writes another member's directory. The only shared file a member branch may change is the deterministically generated super-rar/index.json.

Clock in and out

Use a fresh worktree branch for a shift:

MEMBER="<your-stable-member-id>"
git worktree add "../work-cubby-$MEMBER-shift" \
  -b "cubby/$MEMBER/$(date -u +%Y%m%dT%H%M%SZ)"
cd "../work-cubby-$MEMBER-shift"

WORK_CUBBY_MEMBER="$MEMBER" python3 work_cubby.py clock-in \
  --member "$MEMBER" \
  --task "What I am starting"

# Do the work.

WORK_CUBBY_MEMBER="$MEMBER" python3 work_cubby.py clock-out \
  --member "$MEMBER" \
  --summary "What changed and why" \
  --evidence "https://github.com/owner/repo/pull/123" \
  --evidence "commit:0123456789abcdef"

python3 work_cubby.py verify
git add "cubbies/$MEMBER/show-and-tell/work-ledger.jsonl"
git commit -m "clock: $MEMBER shift"
git push -u origin HEAD
gh pr create --base main

Local cubby

The public repo is the neighborhood projection. Mirror your own sanitized cubby into the canonical local shelf:

python3 work_cubby.py mirror-local --member "$MEMBER"

That writes only to ~/.brainstem/cubbies/<member-id>/. It never writes into the brainstem grail repo and never streams an agent.

Verify

python3 -m unittest discover -s tests -v
python3 scripts/rebuild_super_rar.py --check
python3 scripts/validate.py

No secrets or private transcripts belong here. Evidence should be a public URL, commit SHA, PR, workflow run, or sanitized artifact reference.