Skip to content

docs: add explicit raw-data access guard - #20

Merged
florian6973 merged 1 commit into
mainfrom
docs/raw-data-access-guard
Nov 12, 2026
Merged

florian6973 merged 1 commit into
mainfrom
docs/raw-data-access-guard

Conversation

@florian6973

Copy link
Copy Markdown
Collaborator

Summary

The implementation prompt limits label/prediction-key access and requires approval for demo/full-data runs, but it never explicitly tells the agent not to inspect raw patient-level data. This PR adds an explicit guard.

  • docs/implementation-prompt.md: new RAW-DATA ACCESS GUARD paragraph inside the copyable prompt template, covering all profiles, modes and stages. It forbids directly opening/reading/sampling/previewing/querying real patient records, raw MEDS event files or clinical tables. It also states that a data path, credentials, exploratory mode or an implementation request is not authorization. Local tests must use synthetic fixtures. Only an explicitly human-approved demo/full-data pipeline run may process real inputs, and even then raw rows must never be exposed in output, logs, reports, chat or commits.
  • docs/workflow.md: short summary of the guard.
  • docs/prompt-builder.md: hint shown under "Scope and constraints".
  • docs/tests/prompt_builder.test.cjs: asserts that the guard appears in every rendered prompt variant.

Testing

  • npm test: 9/9 pass (Node 24.20.0)

🤖 Generated with Claude Code

The implementation prompt restricted label access and required approvals
for demo/full-data runs, but never explicitly forbade the agent from
directly inspecting raw patient-level records. Add an explicit guard that
applies across all profiles, modes and stages, mirror it in the workflow
docs and prompt builder, and assert it in the prompt builder tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@florian6973
florian6973 marked this pull request as ready for review November 12, 2026 04:10
@florian6973
florian6973 merged commit c804544 into main Nov 12, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant