{"_id":"@billbliss/architecture-graph","_rev":"2-703e891c8db833462c4b2a57b602f10c","name":"@billbliss/architecture-graph","dist-tags":{"latest":"0.3.1"},"versions":{"0.3.0":{"name":"@billbliss/architecture-graph","version":"0.3.0","license":"MIT","_id":"@billbliss/architecture-graph@0.3.0","maintainers":[{"name":"billbliss","email":"bill@billbliss.net"}],"homepage":"https://github.com/billbliss/architecture-graph#readme","bugs":{"url":"https://github.com/billbliss/architecture-graph/issues"},"bin":{"ag":"bin/ag.js"},"dist":{"shasum":"949c4688a70d42f58b3adac50e6b5526211dbc9e","tarball":"https://registry.npmjs.org/@billbliss/architecture-graph/-/architecture-graph-0.3.0.tgz","fileCount":117,"integrity":"sha512-2vdT+/xYIzNhfNmoGWvK3tl/ea4JDkv/myGrxUe5d6vsTs3gu+V68/3CRYFEV5RsAwOQiROOZ69dkxDroABzbw==","signatures":[{"sig":"MEYCIQC4aagotQHkCpdH0Waof6lEV56hIlvFf37twabfOC91jAIhAKQlP32AhLH3UcuFG4x74K6uNKnRYh1SzkfDVDxZYTho","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":300144},"type":"module","_from":"file:dist/billbliss-architecture-graph-0.3.0.tgz","types":"./lib/index.d.ts","engines":{"node":">=22"},"exports":{".":{"types":"./lib/index.d.ts","import":"./lib/index.js"},"./schema":"./schema/graph.schema.json"},"scripts":{"test":"npm run build && node --test test/*.test.js","build":"tsc -p tsconfig.json && node scripts/schema.mjs","verify":"npm test && npm run test:consumer","package":"node scripts/package.mjs","prepack":"npm run build","test:package":"node scripts/test-package.mjs","test:consumer":"node test/consumer.mjs"},"_npmUser":{"name":"billbliss","email":"bill@billbliss.net"},"_resolved":"/Users/billbliss/dev/architecture-graph/dist/billbliss-architecture-graph-0.3.0.tgz","_integrity":"sha512-2vdT+/xYIzNhfNmoGWvK3tl/ea4JDkv/myGrxUe5d6vsTs3gu+V68/3CRYFEV5RsAwOQiROOZ69dkxDroABzbw==","repository":{"url":"git+https://github.com/billbliss/architecture-graph.git","type":"git"},"_npmVersion":"11.18.0","description":"Portable architectural declarations, context, and derived guidance","directories":{},"_nodeVersion":"22.17.0","dependencies":{"zod":"4.6.1","yaml":"2.9.0"},"publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_hasShrinkwrap":false,"devDependencies":{"typescript":"5.9.3","@types/node":"22.20.2"},"_npmOperationalInternal":{"tmp":"tmp/architecture-graph_0.3.0_1789011462993_0.5198378682662514","host":"s3://npm-registry-packages-npm-production"}},"0.3.1":{"name":"@billbliss/architecture-graph","version":"0.3.1","description":"Portable architectural declarations, context, and derived guidance","type":"module","engines":{"node":">=22"},"bin":{"ag":"bin/ag.js"},"exports":{".":{"types":"./lib/index.d.ts","import":"./lib/index.js"},"./schema":"./schema/graph.schema.json"},"scripts":{"test":"npm run build && node --test test/*.test.js","test:consumer":"node test/consumer.mjs","verify":"npm test && npm run test:consumer","package":"node scripts/package.mjs","test:package":"node scripts/test-package.mjs","build":"tsc -p tsconfig.json && node scripts/schema.mjs","prepack":"npm run build"},"license":"MIT","repository":{"type":"git","url":"git+https://github.com/billbliss/architecture-graph.git"},"dependencies":{"yaml":"2.9.0","zod":"4.6.1"},"devDependencies":{"@billbliss/architecture-graph":"^0.3.0","@types/node":"22.20.2","typescript":"5.9.3"},"types":"./lib/index.d.ts","publishConfig":{"access":"public","registry":"https://registry.npmjs.org"},"_id":"@billbliss/architecture-graph@0.3.1","bugs":{"url":"https://github.com/billbliss/architecture-graph/issues"},"homepage":"https://github.com/billbliss/architecture-graph#readme","_integrity":"sha512-6hTSG+FKVr8YrsdKAsGUFD8I8lIO5twhWvymZxr5tpl6KcgTzTau26NfHlG5Er57wDZqYl8+3aWIG4YW4ZiJ5Q==","_resolved":"/home/runner/work/architecture-graph/architecture-graph/dist/billbliss-architecture-graph-0.3.1.tgz","_from":"file:/home/runner/work/architecture-graph/architecture-graph/dist/billbliss-architecture-graph-0.3.1.tgz","_nodeVersion":"24.20.0","_npmVersion":"11.18.0","dist":{"integrity":"sha512-6hTSG+FKVr8YrsdKAsGUFD8I8lIO5twhWvymZxr5tpl6KcgTzTau26NfHlG5Er57wDZqYl8+3aWIG4YW4ZiJ5Q==","shasum":"d53e85a474e6b9ba407c49e13efddd878943df85","tarball":"https://registry.npmjs.org/@billbliss/architecture-graph/-/architecture-graph-0.3.1.tgz","fileCount":117,"unpackedSize":305419,"attestations":{"url":"https://registry.npmjs.org/-/npm/v1/attestations/@billbliss%2farchitecture-graph@0.3.1","provenance":{"predicateType":"https://slsa.dev/provenance/v1"}},"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEYCIQC6+UwGpy6lml6z57McSoJ0rkR2uXxXYZ5ZvhHdl9jSnQIhAOdNnLIDEauMZgQto7Z+oMjvF2U++AoLIltXKSLxHN2e"}]},"_npmUser":{"name":"GitHub Actions","email":"npm-oidc-no-reply@github.com","trustedPublisher":{"id":"github","oidcConfigId":"oidc:6c2eeb2e-9de6-4b95-b7d8-02474a26d84c"}},"directories":{},"maintainers":[{"name":"billbliss","email":"bill@billbliss.net"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/architecture-graph_0.3.1_1789019533523_0.3148010986683287"},"_hasShrinkwrap":false}},"time":{"created":"2026-09-10T03:37:42.803Z","modified":"2026-09-10T05:52:14.299Z","0.3.0":"2026-09-10T03:37:43.376Z","0.3.1":"2026-09-10T05:52:13.675Z"},"bugs":{"url":"https://github.com/billbliss/architecture-graph/issues"},"license":"MIT","homepage":"https://github.com/billbliss/architecture-graph#readme","repository":{"type":"git","url":"git+https://github.com/billbliss/architecture-graph.git"},"description":"Portable architectural declarations, context, and derived guidance","maintainers":[{"name":"billbliss","email":"bill@billbliss.net"}],"readme":"# Architecture Graph\n\nKeep the reasons behind your software's design close to the code—in any programming language.\n\nAs a project grows, it gets harder to answer simple questions: who owns this responsibility? Which part decides what a value means? What must stay true when we change this interface? The answers often live across design documents, old discussions, and someone's memory. Developers and AI coding agents end up rediscovering them—or making different assumptions.\n\nArchitecture Graph (AG) gives those answers a small, shared home in your repository. It records the important parts of your design and how they relate, so the next change can start with the intended architecture in view.\n\n**AG is designed to be used with a coding agent.** In practice, keeping architectural context current requires the agent to retrieve it before changes and maintain it alongside the code. People provide direction, resolve decisions and review the results. Every command can be run manually, but sustained manual maintenance is not the intended adoption model.\n\nAG is designed for any language or mix of languages. The toolkit runs on Node.js; your application does not have to. See [language support and toolchain impact](docs/languages-and-toolchain.md) for what adoption adds to a non-JavaScript project.\n\n## What you get\n\n- **Useful context before a change.** Find the responsibilities, rules, and decisions connected to the area you are working on.\n- **A design that can grow with the project.** Begin with requirements and proposals before code exists. Keep unanswered questions visible, then connect the design to real files as you build.\n- **Less repeated explanation.** Generate a readable briefing that helps developers and coding agents work from the same understanding.\n- **Checks that catch broken records.** Find references to missing files, conflicting ownership declarations, and guidance that no longer matches the graph.\n\nAG is useful when important design decisions are becoming difficult to remember or explain consistently. A tiny program you can understand at a glance usually does not need it. The [hello-world example](examples/hello-world/README.md) deliberately uses a tiny program to make the workflow easy to see.\n\nAG records what the software is intended to do. It does not prove that the code follows that intent; application tests and review still matter.\n\n## Getting started: three separate steps\n\n1. **Install the toolkit in your project.** This adds the `ag` command, which reads and checks the graph.\n2. **Install the coding-agent skill.** This teaches Claude Code or Codex how to help build and maintain the graph. It comes inside the toolkit download; it is not another service or subscription.\n3. **Create your project's first graph.** Read the project's requirements and design documents, then record the important responsibilities, rules, and open questions. Ask your coding agent to do this work and review its proposals; installation alone does not do it.\n\nYou need a coding agent (Claude Code or Codex), Node.js 22 or later, and npm. The npm installation command for this release is:\n\n```sh\nnpm install --save-dev @billbliss/architecture-graph@0.3.1\n```\n\nYou can also [install from a tarball](docs/github-packaging.md) when testing a local build.\n\n**[Follow the installation and first-graph guide →](docs/getting-started.md)**\n\n## Where to go next\n\n- [Try the hello-world example](examples/hello-world/README.md) to see a design evolve alongside working code.\n- [Explore AG's own architecture](https://github.com/billbliss/architecture-graph/tree/main/examples/architecture-graph) for a larger example that references the toolkit’s real source, contracts, and open decisions. Run this model from a full repository checkout.\n- [Use AG with a coding agent](docs/skill-installation.md)—Claude Code or Codex—to turn your documents into a useful starting graph.\n- [Keep context useful as the graph grows](docs/indexing-and-ci.md) with generated indexes and generation in GitHub Actions.\n- [Look up commands and file formats](docs/reference.md) when you need the details.\n- [Understand the limits and upgrades](docs/compatibility.md) to know what the checks do—and what they cannot tell you.\n- [Download or build a package](docs/github-packaging.md) for your team.\n\nThe [project history](docs/history/README.md) records how AG was created. It is optional background, not part of learning to use the toolkit.\n\nThe toolkit is developed in TypeScript and ships JavaScript ready to run, with types and source maps for developers. Your project owns one YAML graph.\n\nVersion **0.3.1** · [MIT licensed](LICENSE)\n","readmeFilename":"README.md"}