docs: OCI packaging (dockworker) and component stack deploy model

[stevei101]

Summary

• Document org packaging policy: no Dockerfiles; OCI images from Nix (flake.nix) published via dockworker.ai + skopeo
• Define OGRE deploy model as a mash-up of component containers (oxidizedRAG, oxidizedgraph, data-fabric), not a monolithic OGRE image
• Update README.md and PLAN.md Phase 5.3 checklist accordingly

Files

Doc	Purpose
docs/PACKAGING.md	Nix → OCI → dockworker.toml → GHCR
docs/DEPLOY_STACK.md	Component URLs, apply order, future ogre/deploy/

Test plan

This PR (docs only)

• Pre-commit hook passes
• Links and paths render in GitHub

Next: K8s validation (follow-up work, not blocked on this PR)

Prerequisite: oxidizedgraph#44 merged + image pushed to GHCR.

1. oxidizedgraph (first component)

   cd oxidizedgraph
   just image && IMAGE_TAG=0.2.0 just push   # GHCR auth
   # Edit deploy/overlays/gke-autopilot/serviceaccount-wi.yaml
   kubectl apply -k deploy/overlays/gke-autopilot
   kubectl -n oxidizedgraph get pods,svc,pdb
   kubectl -n oxidizedgraph port-forward svc/oxidizedgraph 8080:8080
   curl -s http://localhost:8080/health

2. OGRE stack (after ogre/deploy/ lands)

   • Apply component overlays in order (graph → rag → fabric)
   • Verify cross-namespace egress (fabric HTTPS, graph → fabric events)
   • Smoke: PR-reviewer-style flow (retrieve → execute → persist)

3. Track in ogre

   • Open issue: deploy/base Kustomize mash-up + GKE Autopilot overlay
   • Pin component image digests in overlay after first successful cluster apply

Made with Cursor