Henry Kobutra
← All notes
Companion material

agent work

Agent work examples

Synthetic, standard-library examples for the two draft Notes. No network, client account, credentials or package installation is required. Use Python 3.9 or newer. Copy this whole directory into a writable scratch folder before running it. The shell setup command assumes a POSIX shell.

Acceptance demo

Run python3 demo.py from the copied directory. It creates and removes a temporary child directory. Expect the boundary test to fail on the deliberately buggy implementation, then all three tests to pass on the correction. The driver exits zero only if both phases match those expectations. Source fixtures remain unchanged. Read deadline/test_expiry.py and compare deadline/expiry.py with deadline/expiry_fixed.py.

Reuse acceptance-template.md for scope, checks, evidence and an acceptance decision. This exercise proves only integer timestamp comparisons, not a production expiry or authorization system.

Shared context setup

The companion manuscript ../../articles/shared-project-context.md contains the AGENTS.md template. Save it manually as context/AGENTS.md before using this example as a complete context map. The entry point is supplied as a manuscript template rather than an installed instruction file.

Copy deadline/expiry.py and deadline/test_expiry.py into context using the manuscript's setup command. Run the context checker from this directory, then start a fresh coding session rooted in context and explicitly paste the startup prompt. CLIENT-START.md is not a claimed automatic client entry point.

The checker command is python3 check_context.py context CLIENT-START.md AGENTS.md. It must exit 1 until the missing entry point is supplied. Its own test command is python3 -B -m unittest -v test_context_check. Those tests build ordinary Markdown fixtures under the working directory and remove them afterwards. They do not write any agent instruction files or exercise a coding client.

The checker supports simple inline Markdown links with plain relative paths. It rejects recognized absolute, remote, fragment and outside-root targets. It does not parse full Markdown, validate prose or prove client compliance. Do not use it as a security boundary or a general repository crawler.

A conversation starts somewhere

What are you
working on?

If something here connects with what you're working on, email me.

henry@kobutra.com