grant Council agents read access to the personal knowledge base
Every voting member's persona now documents that the PKB (daily/, inbox/, notes/, projects/, reading/, reflections/, reviews/, all of sessions/) is readable. Write access stays unchanged: voting members write only to their own members/<slug>/ directory; the Researcher writes only to sessions/<slug>/research/. The read-scope block distinguishes the two invocation contexts: /council runs stay bounded to the brief + research package + debate packet (the PKB isn't pulled into formal deliberation unless the Moderator explicitly points at a note), while /ask-*, /reflect, /triage-inbox, /review-week, and /review-month may pull PKB context selectively as the lens requires. Researcher gets a parallel note that PKB content is now legitimate primary-source material alongside web searches during Phase-1 research, flagged as source: pkb in the resulting research files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Claude Opus 4.7
@@ -40,6 +40,16 @@ You may write **only** inside `members/holt/`. Never touch other agents' memory
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/holt/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/holt/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/koskela/`. Never touch other agents' memo
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/koskela/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/koskela/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/lindholm/`. Never touch other agents' mem
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/lindholm/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/lindholm/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/okafor/`. Never touch other agents' memor
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/okafor/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/okafor/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/prochazka/`. Never touch other agents' me
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/prochazka/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/prochazka/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -25,6 +25,14 @@ You are invoked by the Moderator at two points per session, at most:
|
||||
|
||||
- **Phase 3b — Follow-up research** (only if triggered). The Moderator may re-invoke you with a consolidated list of `Research gap` questions raised by the Council during debate. You produce additional research files with frontmatter `round: 2`.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond the vault's session directory, the user maintains a personal knowledge base: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`. You have read access to all of it.
|
||||
|
||||
During Phase-1 pre-session research for `/council`, you may use PKB notes as primary sources alongside web searches — a user-written permanent note on topic X is legitimate citation material, flagged as `source: pkb` in the resulting research file. When the user's own notes contradict external sources, name the disagreement without resolving it.
|
||||
|
||||
Write access is unchanged: only `sessions/<slug>/research/`.
|
||||
|
||||
## User clarification — available any time during Phase 1
|
||||
|
||||
You may return a `## User clarification needed` section at **any point during your Phase-1 work** — before starting (if the brief is too vague to research usefully) or mid-research (if ambiguity surfaces once you start digging). Keep it to 1–3 concrete questions only the user can answer. When you flag clarifications, return early without completing the research; the Moderator will ask the user, append the answers to `brief.md`, and re-invoke you with the updated brief.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/tavsan/`. Never touch other agents' memor
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/tavsan/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/tavsan/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/tintori/`. Never touch other agents' memo
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/tintori/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/tintori/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/vaasa/`. Never touch other agents' memory
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/vaasa/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/vaasa/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/vale/`. Never touch other agents' memory
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/vale/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/vale/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
@@ -40,6 +40,16 @@ You may write **only** inside `members/vire/`. Never touch other agents' memory
|
||||
|
||||
In Phase 5 (Memory update), append one entry to `journal.md` (newest on top). Update `on-the-user.md` and `revisit.md` only if something genuinely non-obvious came up this session — do not pad.
|
||||
|
||||
## Personal Knowledge Base access
|
||||
|
||||
Beyond your `members/vire/` memory, you have **read access to the user's full knowledge base**: `daily/`, `inbox/`, `notes/`, `projects/`, `reading/`, `reflections/`, `reviews/`, and all `sessions/`. You may read anything in the vault that would help you answer usefully — a daily note, a project log, a permanent note, a reading note, a past session outcome.
|
||||
|
||||
Write access is unchanged: you write only to your own `members/vire/` directory.
|
||||
|
||||
When invoked via `/ask-*`, `/reflect`, `/triage-inbox`, `/review-week`, or `/review-month` — read selectively. Pull the specific files you need, not the whole vault.
|
||||
|
||||
When invoked via `/council` — stick to the brief + research package + debate packet. Do not pull from the PKB unless the Moderator explicitly points you at a note.
|
||||
|
||||
## Web access
|
||||
|
||||
You cannot browse the web. The shared research package at `sessions/<slug>/research/` is your evidence base. If you need something that's not there, raise a `## Research gap` section in Phase 3 output (one or two concrete, searchable questions). The Moderator will re-engage the Researcher.
|
||||
|
||||
Reference in New Issue
Block a user