Atmosphere — Prompts
Atmosphere is a JVM framework. Its "prompts" are Java annotations and configuration code, not natural-language files. The most relevant prompt-like artifacts are the developer governance instructions.
AGENTS.md (Root — Developer Instructions)
## Build System: Maven
**This project uses Apache Maven with the Maven Wrapper (`./mvnw`).**
## Git Workflow
### Hooks Setup
**Run this at the START OF EVERY SESSION:**
git config core.hooksPath .githooks
**NEVER use `--no-verify` when committing or pushing.** The hooks enforce:
- Apache 2.0 copyright headers on all Java source files
- No unused or duplicate imports in staged Java files
- Commit message format (max 2 lines, conventional commits recommended)
- No AI-generated commit signatures
- Pre-push: Maven build must pass
### Commit Message Format
Use conventional commit prefixes. The commit-msg hook warns if missing:
type(scope): description
Rules enforced by hooks:
- Maximum 2 non-empty lines (summary + optional detail)
- First line under 100 characters
- NEVER add `Co-authored-by: Copilot` or any AI co-author trailer — the commit-msg hook will reject it
- Do not add ANY trailer lines (Co-authored-by, Signed-off-by, etc.) to commit messages
Prompting technique: Hard prohibition list with enforcement mechanism (git hooks). The explicit "NEVER add Co-authored-by" rule is a compliance policy preventing AI attribution footprints in commit history — unusual in the corpus.
.claude/hooks/check-drift-log.sh (Stop Hook)
# High-precision drift-correction patterns:
patterns=(
'stale memory'
'\boff-by-one\b'
'I (was wrong|claimed)[^.]{0,120}(but|actual|truth)'
'memor[a-z]+[[:space:]]+(was|is)[[:space:]]+(wrong|stale|out of date)'
'fabricated[[:space:]]+(rule|stat|count|claim)'
'verified by grep[^.]{0,60}(disagree|contradict|wrong|stale)'
)
# If drift-correction language detected but .harness/drift-log.md NOT updated:
{
"decision": "block",
"reason": "Drift correction language detected in session transcript, but
.harness/drift-log.md was not modified this session. Per feedback_drift_log.md,
every caught drift gets a structured entry (date, claim, truth, slip path, gate added)
appended in the same session."
}
Prompting technique: Meta-cognitive accountability enforcement. The Stop hook detects when an AI assistant acknowledged it was wrong (drift correction) but failed to document the error in the drift log. It blocks the session from ending and demands structured retrospection. This is a novel pattern — using lifecycle hooks to enforce epistemological accountability on the AI agent.
Cedar Policy (Runtime Governance)
permit (
principal in Group::"support-agents",
action == Action::"invoke",
resource is Agent
)
when { context.business_tenant_id != "blocked-tenant" };
forbid (
principal,
action == Action::"invoke",
resource == Agent::"finance-agent"
)
unless { principal in Group::"finance-cleared" };
Prompting technique: Declarative admit/deny policies in AWS Cedar language — deterministic, auditable, not LLM-based.