coulomb/emergent-security
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record a named recipient role separately from its repository.

Browse source 
The probe asked for a repository whenever the role was outside a short
example list, so the session owner was recorded as glas-harness. The card
already names that role. Sources still carry the supporting repository.

Assistant: grok
Assistant-Session: 01a10286-9185-7bb2-b411-89cf6ab4c0c6
This commit is contained in:
tegwick 2026-10-03 23:01:30 +02:00
parent 9c864cc70a
commit 50ff797f76
1 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
tools/probe_provider.py
View file

@ -97,8 +97,10 @@ def main():
"do not use outside sources or perform any actual operation. Return ONLY JSON with "
"package_version, startup_marker (from start.md), retrieval_marker (from access.md), "
"and answers: [{id, route, disposition, sources, reason}]. Route means the actual "
"next recipient (a human role such as delegator, platform, tenant-admin, root-steward "
"or pep-owner when appropriate, otherwise the owning repository), NOT the source "
"next recipient. When the card names that recipient as a role, record the role and "
"keep the supporting repository in sources. Session owner, delegator, platform, "
"tenant-admin, root-steward, and pep-owner are roles. When the card names a "
"repository as the recipient, record that repository. Route is not the source "
"of documentation. Use a concise action for disposition, comma-separated exact source owner IDs "
"listed in the relevant card for sources, and a one-sentence explanation. Cite the "
"most specific source, including emergent-security for its generic envelope and "