handoff: brief — selfco persistent/syncable/shareable/private - #358
Merged
Conversation
Spawn prompt for a fresh session on the vault's access architecture. Framing the brief carries: the four properties are NOT equally open. adr:vault-multi-surface-access already decides persistence and sync (private GitHub repo as source of truth, connector for the apps), so those are execution debt, not design questions. SHAREABLE is the undecided axis and the one that ADR-0070 explicitly does not address — it solved multi-surface access for one person, not access for other people. Two verified findings the next session would otherwise re-derive: - ADR-0070's autocommit.sh is specified but NOT installed at ~/selfco/scripts and no launchd job is loaded, so writes that bypass the /vault skill do not sync at all. - core-library's build/deploy path republishes the entire private vault graph to a public URL; the git vector was closed today but the deploy vector is open, and 'not deployed' is the only containment. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
Skill Audit — PR #358Skills used during development
Recommended skills (based on diff analysis)
Coverage
Generated by skill-audit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Spawn prompt for a fresh session on the selfco vault's access architecture. Self-contained — the new session can be pointed at the file instead of a paste.
The framing the brief carries: the four properties are not equally open.
adr:vault-multi-surface-access(Accepted) already decides persistence and sync — private GitHub repo as source of truth, official connector for web/iPhone/Desktop, local mcp-obsidian on the Mac. Those are execution debt. Shareable is the undecided axis, and it is exactly what ADR-0070 does not address: it solved multi-surface access for one person, not access for other people.Two findings recorded so the next session doesn't re-derive them:
ADR-0070 specifies
scripts/autocommit.sh(fswatch → pull/commit/push + launchd) to catch writes that bypass the /vault skill. The script exists in core's vault skill but is not installed at~/selfco/scripts/, and no launchd job is loaded (the two selfco-box plists are.disabled). Skill-mediated writes sync; hand-edits in Obsidian and mcp-obsidian writes do not.The accidental-sharing leak path found while closing TeamBot public-evidence boundary #321:
core-libraryregenerates the entire vault graph intopublic/graph/selfco.jsonon every build and fetches it at runtime. The git vector was closed today (core-library@ccbf853), but the build/deploy vector is open — "not currently deployed" is the only containment. It is framed in the brief as a design input rather than a bug: a working example of what "shareable" looks like when nobody decided it.The brief routes to /grill-with-docs first and tells the session to escalate to /wayfinder if the sharing model proves genuinely foggy. It explicitly forbids fixing the core-library leak unilaterally — the guard choice is a design decision.
🤖 Generated with Claude Code