{
  "markdown": "# Pulumi Platform OKF Bundle\n\nAn [Open Knowledge Format](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) (OKF v0.1) knowledge bundle for a Pulumi platform team: the runbooks, decision records, and service pages that infrastructure as code never captures, in a format any coding agent can traverse.\n\nCompanion repo to the Pulumi blog post [Knowledge as Code: The Memory File Just Got a Spec](https://www.pulumi.com/blog/knowledge-as-code-the-memory-file-just-got-a-spec/).\n\n## What's inside\n\nThe bundle root is [`platform/`](platform/):\n\n```\nplatform/\n├── index.md                              # Progressive disclosure: what's in the bundle\n├── log.md                                # Append-only update history\n├── services/\n│   ├── index.md\n│   ├── checkout-api.md\n│   └── payments-worker.md\n├── runbooks/\n│   ├── index.md\n│   └── rotate-database-credentials.md\n└── decisions/\n    ├── index.md\n    └── why-we-pin-the-vpc-cni-version.md\n```\n\nEvery concept document carries YAML frontmatter with the one field OKF requires (`type`) plus the recommended ones (`title`, `description`, `resource`, `tags`, `timestamp`). Where a concept describes a real piece of infrastructure, `resource` holds the Pulumi URN of that resource, so an agent can walk from a planned change to the runbook and the decision record that constrain it.\n\n## Use it with your agent\n\n1. **Teach your agent the standard.** Paste the [OKF spec](https://github.com/GoogleCloudPlatform/knowledge-catalog/blob/main/okf/SPEC.md) into your coding agent and tell it this is the format the bundle follows.\n2. **Point it at the bundle.** Clone this repo (or hand the agent the repo URL) and tell it the bundle root is `platform/`. It should read `platform/index.md` first and drill down only when a concept is relevant.\n3. **Ask questions.** For example:\n   - \"Which services touch the payments database?\"\n   - \"Walk me through rotating the payments database credentials.\"\n   - \"Why is the VPC CNI version pinned, and when should we revisit that?\"\n\n## Notes\n\nThe content is illustrative: a fictional platform (one EKS cluster, two payment services, one Postgres instance). The shapes are real, the incident dates are not. Use it as a starting point for your own bundle — the fastest way is to hand your agent the spec plus your existing docs folder and have it refactor them into this structure.\n\nLicensed under the [MIT License](LICENSE).\n",
  "bytes": 2431,
  "sha": "0153dba19aa3792bec7d0c5869af11525b221ec99067841f44a0ca9dafdac550",
  "repo_slug": "dirien/pulumi-platform-okf-bundle",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/okf_dirien_pulumi_platform_okf_bundle_platfo_586dad14/readme"
}