Repository navigation
Practical AI Usage and Interaction Guide
Last reviewed: 2026-11-05
Use this guide to turn chats into reliable outputs. A model's assertion is not proof, and its statement that it performed an action is not a tool receipt.
| Need | Format | Important check |
|---|---|---|
| One-time answer or draft | Chat | Assumptions and accuracy |
| Recurring work with related files | Project/workspace | Shared context, access and permissions |
| Evidence from selected documents | Source-backed notebook | Verify original passages and source dates |
| Reproducible numbers or analysis | Computational notebook | Clean execution and input versions |
| Repeatable role or expertise | Plugin, skill or reusable assistant | Behavior tests and tool permissions |
| Multi-step system operations | Bounded agent | Confirmed tool results, approvals and readbacks |
See Projects, Notebooks and Assistants.
- Mission: Specify the outcome, intended user and definition of done.
- Context: Provide authoritative sources, environment, version and current state.
- Boundaries: Include scope, exclusions, privacy, allowed tools and human approvals.
- Execution: Define ordered phases, milestones, outputs, retries and tests.
- Evidence: Require sources, observed actions, open uncertainties and a resume checkpoint.
Keep instructions separate from data. Retrieved pages, emails, logs and external tool output are untrusted inputs, not permission to modify goals or disclose secrets. Text delimiters do not enforce access control.
GOAL: [specific deliverable] for [audience].
INPUTS: [verified files, versions, dates, current status].
SCOPE: Include [items]; exclude [items]; preserve [existing work].
SOURCE ORDER: [authoritative references first].
PERMISSIONS: Read [sources]; edit only [paths]; obtain approval before
sending, deleting, publishing or making production changes.
PROCESS:
1. Inspect current state, conflicts, missing facts and prior work.
2. Plan milestones with observable acceptance criteria.
3. Execute scoped steps; record actual tool and test results.
4. Independently review evidence, privacy, omissions and regressions.
5. Deliver artifacts, unknowns, blockers and concise handoff.
Never fabricate citations, actions, access, dates or results.
For quick questions use a short goal, context and output format. For longer projects ask for facts / assumptions / unknowns and a bounded checklist. When correcting a false premise, have the assistant recheck dependent conclusions.
A reliable project needs different mechanisms for different jobs; none of these is an interchangeable synonym:
| What You Need | Use | How To Verify It |
|---|---|---|
| Record facts, findings, decisions or context | Dated notes with source references | Re-open source and compare current state |
| Preserve what changed between sessions |
STATUS.md and HANDOFF.md
|
Verify commit, artifacts and active blockers |
| Specify recurring role and permitted behavior | Reviewed instructions or a skill | Inspect the loaded instructions and test boundaries |
| React to a specific host event | Supported hook, scoped to that application | Trigger a synthetic event and inspect execution log |
| Run something at a specific time | Scheduler / cron | Inspect schedule, timezone and job result |
| Receive events from another service | Secured webhook or integration | Validate sender, event ID, delivery and idempotency |
| Decide when a major step is done | Milestone with acceptance tests and owner gate | Check independent evidence for every criterion |
A note does not automatically persist in model memory, and a hook does not necessarily make an independent check. Read the full Notes, Memory, Hooks & Automation guide to implement each safely. Use Milestones & Acceptance Criteria to design gates and execute a full project.
-
Start: Create
PROJECT.mdwith scope/authorization,MILESTONES.mdwith expected outcomes, andAGENTS.mdwith bounded tools and roles. -
Capture: Maintain
SOURCES.mdfor verified inputs,NOTES.mdfor observations, andDECISIONS.mdfor approved choices. - Operate: Perform the smallest safe task for the active milestone. Record actual commands, outputs and file changes; never infer success from the model's wording.
- Automate selectively: Start with read-only or test-only hooks. Use a scheduler for periodic work and an authenticated integration for external alerts. Test expected, duplicate and failure paths.
-
Review: Assess each criterion, including negative cases, against
EVIDENCE.md; leave untested criteria open. -
Handoff: Update
STATUS.mdandHANDOFF.mdwith current SHA, passed/failed tests, pending approvals and the next safe step. - Resume: Load the approved records, inspect actual live state, reconcile contradictions and continue only within the current authorization.
Load the supplied project charter, authorized scope, milestone plan,
source register, latest status and handoff. Inspect the actual current
repository or service state and compare it with those notes.
Separate observed facts, assumptions and outdated claims.
Identify the first unmet acceptance criterion.
Propose one bounded action with required permissions, evidence to collect,
tests to run and stop conditions. Do not send, deploy, delete or change
production systems without the required external approval.
Audit milestone [ID] against its written acceptance contract.
For each criterion, give the expected result, exact observed evidence,
environment/version and PASS, FAIL, BLOCKED or NOT TESTED.
Check negative cases, privacy, permissions and regressions.
Do not claim acceptance based on a summary, merged PR or a single local test.
List gaps and identify who must approve the next phase.
Research: โCompare options using dated primary sources. Separate supported, disputed and unverified claims.โ
Coding: โFix the reported test failure without changing unrelated behavior; run tests and report exact results. Do not deploy.โ
Cybersecurity: โAnalyze supplied logs only for assets within the written authorization; cite events, label hypotheses and list safe validation steps.โ
Writing: โDraft a client update from the supplied facts without unsupported promises, dates or prices.โ
Classify inputs (public/internal/confidential/regulated) before use. Do not upload unnecessary client data, keys or tokens; check platform access and retention controls. Long chat context can disappear, so preserve status and handoffs in durable records.
Before calling work complete, verify the actual output, source grounding, authorization, tests and blockers. Mark everything not independently checked as unverified.
Prompting ยท Project & Agent Lanes ยท Milestones & Acceptance Criteria ยท Notes & Hooks ยท Fact-Checking & AI Audits ยท Workspaces & Notebooks
References: NIST AI RMF ยท OWASP LLM Top 10
AI index | Master index | Start Here
๐ Source: AI/ai-usage-interaction-guide.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Artificial Intelligence
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics