Aet investigate
Skill AdvancingTitans/agent-engineering-toolkit/skills/aet-investigate
Create a bounded, read-only investigation from normalized Codex or Claude Code Run Records, optionally inspect explicit AET Proof and Freshness records, and export a Portable Evidence Bundle for an independent reviewer.From its SKILL.md
npx -y skills add AdvancingTitans/agent-engineering-toolkit --skill aet-investigateAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.1 KB, 651 tokens by cl100k_base, as published. Nobody here has run it
/aet-investigate
Answer one declared investigation question with a portable evidence handoff.
Boundary
- Keep the target workspace read-only.
- Do not execute arbitrary commands, modify code, commit, push, merge, publish, or repair.
- Require one primary hypothesis, at least one competing hypothesis, and a disconfirming search.
- Treat Run Records as historical behavior. They may create Observations and
Evidence Candidates, but only explicit
proof.inspectandfreshness.checkresults may create Verified Evidence. - Preserve
unknown, counter-evidence, diagnostics, Freshness limitations, and everydoes_not_provestatement. - Use
policy.jsonandtool-contract.jsonwithout expanding their authority.
Workflow
-
Normalize one declared run when a normalized directory is not already available:
aet run normalize --source <codex|claude-code> \ --input <session.jsonl> --output <normalized-run> -
Create an
investigation-request/1.0JSON object. Bind itsrun_sourcesentry to the normalized Manifest'ssource_typeandrun_group_id. Copy the budgets and privacy boundary frompolicy.json; narrow them when possible. -
Run the investigator. Without a Proof it remains observation-only:
aet investigate --request <request.json> \ --run <normalized-run> --output <investigation.json>To inspect an existing deterministic Proof, the Policy must allow
proof.inspectandfreshness.check, and their budgets must be non-zero:aet investigate --request <request.json> \ --run <normalized-run> --workspace <workspace> \ --proof <proof.json> --output <investigation.json>The Proof path and its recorded workspace must remain inside and match the declared read-only workspace. A matching recorded command Candidate may be marked
verified; stale Proof remains historical Evidence and cannot answer a current-workspace Claim. -
Compile and validate the handoff:
aet bundle create --investigation <investigation.json> \ --output <evidence-bundle> aet bundle validate <evidence-bundle> -
Return only the bounded status, unresolved questions, Bundle path, and the smallest authorized next action. A reviewer does not need AET installed to read
manifest.json,index.json,core/*.jsonl, andreport.md.
Completion check
Claim completion only when aet bundle validate <evidence-bundle> returns
PASS. Confirm the Investigation preserves the original Policy and Ledger,
does not promote Agent self-report, and exports real Run Group, Record identity,
Proof, Freshness, Source type, and Content Hash bindings. A non-unknown
finding requires current deterministic Evidence.
Stop after the validated Bundle. Do not continue into repair, new command execution, Learn, Stage, Adopt, or release work.
What ships with it: 3 files
3.0 KB alongside SKILL.md
- output-schema.json1.0 KB
- policy.json852 B
- tool-contract.json1.2 KB