Manual context packet

A context packet is the working set prepared for one task.

It should contain enough evidence to act correctly, but not every available file, conversation, or remembered fact.

This example comes from a real bug in this guide: the homepage linked to the Markdown source path for the inference page, so the deployed site returned a 404.

The packet

task:
  id: guide-fix-inference-link
  request: Fix the inference link on the guide homepage.
  observed_url: https://guide.hills-lab.hr/concepts/inference.md
  observed_result: 404
  expected_url: https://guide.hills-lab.hr/concepts/inference/

scope:
  repository: github:hrvojepavlinovic/trustworthy-agent-memory
  allowed_changes:
    - src/content/docs/index.md
  out_of_scope:
    - rewriting the inference article
    - changing route configuration
    - changing unrelated links or copy

evidence:
  - source: src/content/docs/index.md
    claim: The homepage link points to ./concepts/inference.md.
    authority: current repository source
  - source: src/content/docs/concepts/inference.md
    claim: The inference page exists as a Starlight content page.
    authority: current repository source
  - source: astro.config.mjs
    claim: The configured Starlight slug is concepts/inference.
    authority: current repository source

environment:
  package_manager: pnpm
  source: package.json#packageManager
  command_availability: unknown

decision:
  replace: ./concepts/inference.md
  with: /concepts/inference/
  reason: Public links must use the generated site route, not the Markdown source path.

verification:
  - run the repository's format check
  - run the repository's Astro check
  - run the repository's production build
  - confirm dist/concepts/inference/index.html exists
  - confirm the homepage Inference link contains no .md route
  - after deployment, request /concepts/inference/ and expect HTTP 200

Why each part is present

task records the failure and the expected behavior. “Fix the link” alone would force the agent to infer both.

scope limits the change. The agent does not need permission to rewrite the article or reorganize routing.

evidence separates observed facts from instructions. Each claim points to something that can be checked again.

environment records the declared package manager without claiming that its command is available in the current shell.

decision makes the intended route explicit. This is useful when source file paths and public URLs follow different conventions.

verification covers both the repository and the deployed result. A passing Markdown edit is not proof that the public route works.

What is deliberately missing

This packet does not include the full repository tree, article text, git history, brand notes, provider research, server configuration, or unrelated user preferences.

None of those change the correct action.

The packet is useful because it removes retrieval work without hiding the evidence needed to verify its claims.

Result

The real fix changed the guide’s Markdown source links to generated site routes. The relevant change is public in commit baffd67.

The context packet comparison found that the packet did not improve this task. Its first version mixed evidence with generated output, assumed a package-manager command was available, and used a verification rule broader than the task. Those errors were removed here.