Context Architecture for Enterprise Agentic Software Delivery

This repository contains the public source for the whitepaper Context Architecture for Enterprise Agentic Software Delivery.

The paper argues that enterprise agentic software delivery needs more than larger context windows or better prompts. It needs a context architecture: a boundary model and operating model that make domain language, ownership, authority, memory, handoffs, review, governance, and accountability explicit enough for agentic work to remain bounded and trustworthy.

Repository Shape

• paper/whitepaper.yml: publication metadata, front-matter source, chapter order, and running-title configuration.
• paper/front-matter/: standalone front-matter Markdown, including the model overview.
• paper/chapters/: reader-facing whitepaper chapters, numbered in public reading order.
• paper/figures/specs/: YAML sources for generated publication diagrams.
• paper/figures/renderer.yml: shared style tokens and defaults for generated diagrams.
• paper/figures/DIAGRAM_DESIGN_SYSTEM.md: visual rules for the diagrams.
• paper/scripts/: deterministic build and diagram rendering scripts.
• paper/styles/publication.css: PDF print styling.
• context/: public maintenance context for editorial rules, glossary, source grounding, checklist, and review workflow.
• .codex/skills/: optional Codex skills for maintaining the paper.
• .github/: planned issue, PR, build, artifact, and release workflow.

The generated PDF is intentionally not committed. It is built from source and attached to GitHub Actions artifacts and versioned GitHub Releases.

Build Locally

Install the local dependencies:

python3 -m pip install -r requirements.txt

Required command-line tools:

• pandoc
• weasyprint
• rsvg-convert from librsvg2-bin for PNG diagram previews
• pdfinfo from poppler-utils for PDF metadata checks

Build the whitepaper:

make build

The generated PDF is written to:

build/context-architecture-whitepaper.pdf

Review Workflow

Use GitHub Issues for review tasks and GitHub Pull Requests for changes:

1. Open one issue per concrete review point or release task.
2. Create a branch for the fix.
3. Open a PR that links the issue.
4. Let CI build the whitepaper and upload the generated PDF artifact.
5. Review the PDF artifact and source diff together.
6. Merge only when the source and generated paper both read cleanly.

Versioned PDFs should be published through GitHub Releases from SemVer tags, not committed into the repository. Drafts are prereleases of the first stable publication, for example v1.0.0-draft.1; the first real publication target is v1.0.0.

License

Whitepaper text, figure specs, generated figures, and public context documents are licensed under Creative Commons Attribution 4.0 International.

Build scripts and workflow files are licensed under the MIT License.

See LICENSE.md.