{
  "case_studies": [
    {
      "category": "windows-desktop",
      "evidence_basis": "retained_delivery",
      "evidence_coverage": "A retained local Release-build and UI-automation record opened the sound document and observed its named sections. Committed loader and renderer source were inspected at the later review date.",
      "id": "case-windows-desktop",
      "implemented_result": "A document pane loads a local sound knowledge file and renders its headings, technique tables and effects notes. A source hint shows which document was opened.",
      "limits": "This case establishes the local document-reading path. It does not validate the musical advice, audio processing, hardware control or a deployed service. The application was not rerun for this editorial review.",
      "platform_fit": "The demonstrated job already uses a Windows application and local knowledge files. A native document pane keeps those files in the established desktop workflow without requiring a hosted account.",
      "problem": "A musician needs structured notes about a sound while working in an existing Windows application.",
      "remaining_costs": "A Windows machine, local document storage, application and component maintenance, and any applicable component licences remain.",
      "reuse": "The existing sound records supply a fallback when a document is absent. The pane uses the application theme and docking surface instead of introducing another viewer.",
      "reviewed_at": "2026-09-30",
      "status": "demonstrated",
      "title": "Keep sound knowledge beside the working tools",
      "verification_date": "2026-09-24"
    },
    {
      "category": "web-product",
      "evidence_basis": "retained_delivery",
      "evidence_coverage": "The retained website delivery records 66 passing Python checks and Windows Edge journeys at desktop and two phone viewport sizes, including comparison dialogs, local resources, clean replay and rollback.",
      "id": "case-web-product",
      "implemented_result": "A static product site presents a workflow, practical lessons, scoped comparisons and a dated evidence ledger. Approved releases can be revisited and the selected edition can be rolled back.",
      "limits": "Phone viewport emulation does not establish real iOS behaviour. Public hosting and real-device acceptance belong to the deployment work. These checks establish the retained local edition, not availability or a productivity gain.",
      "platform_fit": "A browser fits read-only distribution across desktop and phone-sized screens. A static artifact can be inspected without granting a visitor access to the operational system.",
      "problem": "Product visitors need readable delivery evidence while operational source records stay private.",
      "remaining_costs": "Hosting, domain management, editorial review, retained-release storage and ongoing accessibility and dependency checks remain; their costs are not measured here.",
      "reuse": "Three earlier delivery stories were adapted into lessons about dated evidence, independent work and requested versus observed settings. The publication keeps the existing immutable-release and rollback mechanism.",
      "reviewed_at": "2026-09-30",
      "status": "demonstrated",
      "title": "Publish useful evidence without exposing the workspace",
      "verification_date": "2026-09-30"
    },
    {
      "category": "network-documentation",
      "evidence_basis": "retained_delivery",
      "evidence_coverage": "Retained July checks record successful builds and UI automation of inventory navigation, source badges, host grouping and component drill-through. Committed topology code names the earlier diagram lesson. The source and destination build-check files preserve the shared pattern with later differences.",
      "id": "case-network-documentation",
      "implemented_result": "A Windows topology browser reads collected infrastructure records and shows inventory, queued work and documentation-coverage badges. Application diagrams add host grouping and drill-through with a breadcrumb.",
      "limits": "This is documentation and collection-coverage visibility. It is not continuous network monitoring, a current network-health assessment or an alerting service. July UI checks were reviewed, not rerun; copied patterns are not automatically kept in sync.",
      "platform_fit": "The job uses local collected files and an established Windows administration workflow. The viewer can read those records without publishing the private network to a website; this case does not establish live device access.",
      "problem": "An operator needs to move from a system map to machine inventory and understand stale or missing documentation.",
      "remaining_costs": "Collectors, data freshness, storage, access control, Windows and UI-component maintenance remain. Private network inventory and screenshots are excluded.",
      "reuse": "The infrastructure browser applied a diagram lesson from the music application: generate connectors from the data model and explicitly position runtime nodes when automatic layout does not apply. A theme-colour build check was also adapted from a separate local analysis application.",
      "reviewed_at": "2026-09-30",
      "status": "demonstrated",
      "title": "Read the infrastructure through its recorded evidence",
      "verification_date": "2026-07-14"
    },
    {
      "category": "subscription-replacement",
      "evidence_basis": "gap_review",
      "evidence_coverage": "The retained retirement decision records removal of the candidate and the unperformed real-recording review. No accepted replacement workflow, subscription cancellation or matched cost record was found in the selected evidence.",
      "id": "case-subscription-replacement",
      "implemented_result": "No subscription replacement is established by the reviewed portfolio. An earlier local audio candidate was retired before its required review on representative recordings.",
      "limits": "Evidence gap. To establish a replacement, name the exact recurring job and former service, validate representative inputs and quality, confirm which workflow actually stopped needing the service, and record the remaining costs. No savings or ROI is claimed.",
      "platform_fit": "A local Windows tool could fit files already on the machine. That is a platform rationale only; it does not establish that the paid service job has been replaced.",
      "problem": "A local tool may cover a paid service task, but replacing a subscription requires evidence of the exact work and acceptable quality.",
      "remaining_costs": "A future comparison must include compute, electricity, storage, setup, quality review, maintenance, licences and any remaining paid service; all amounts and net savings are unmeasured.",
      "reuse": "The portfolio reuses the rule that a requested result and an observed result stay separate. Retired or unchecked candidates do not become current product successes.",
      "reviewed_at": "2026-09-30",
      "status": "evidence_gap",
      "title": "A replacement needs proof of the job it replaces",
      "verification_date": "2026-09-24"
    }
  ],
  "generated_at": "2026-09-30T05:48:14+00:00",
  "overview": {
    "summary": "VIBE-OS connects goals, project work and delivery evidence around Codex and Claude Code. Define the outcome, let a supported coding agent carry out the work, then inspect the checks and the result. Keep useful decisions and examples available for the next project.",
    "title": "Get useful work from your agents. Keep what you learn."
  },
  "records": [
    {
      "checked_at": "2026-09-30",
      "evidence_basis": "local_verification",
      "evidence_date": "2026-09-29",
      "example": "The original local publication retained previous assets while changing the selected release.",
      "id": "repeatable-releases",
      "kind": "evidence",
      "limits": "Historical local validation does not establish public hosting, availability or security guarantees.",
      "mechanism": "Build a complete snapshot, verify it, then switch the active entry.",
      "relevance": "Publishing evidence without losing the last known working result.",
      "status": "demonstrated",
      "summary": "A dated local verification exercised immutable releases, unchanged-input refresh, failure protection and rollback.",
      "title": "A checked release can be revisited",
      "tradeoffs": "Retaining releases uses storage and requires deliberate selection of what may be published."
    },
    {
      "checked_at": "2026-09-30",
      "evidence_basis": "editorial_adaptation",
      "evidence_date": "2026-09-29",
      "example": "A monthly report keeps missing resource measurements unreported.",
      "id": "evidence-stays-dated",
      "kind": "lesson",
      "limits": "Delivery counts alone do not measure productivity or business value.",
      "mechanism": "Read one committed source snapshot and preserve the evidence cutoff.",
      "relevance": "Deciding what shipped and what the available measurements can support.",
      "status": "demonstrated",
      "summary": "A delivery report turns recorded work into a dated evidence view.",
      "title": "Keep a result tied to its evidence",
      "tradeoffs": "Incomplete historical records limit conclusions even when a report builds successfully."
    },
    {
      "checked_at": "2026-09-30",
      "evidence_basis": "editorial_adaptation",
      "evidence_date": "2026-09-29",
      "example": "An optional preference can use a reversible default while a required decision retains its hold.",
      "id": "continue-independent-work",
      "kind": "lesson",
      "limits": "This explains a tested local policy; no measured throughput gain is claimed.",
      "mechanism": "Keep blocked work and its evidence; inspect whether other work is independent.",
      "relevance": "Avoiding unnecessary waiting while preserving unfinished work.",
      "status": "demonstrated",
      "summary": "A bounded delivery policy distinguishes optional preferences from required decisions.",
      "title": "Continue useful work around a genuine blocker",
      "tradeoffs": "Independence and file ownership require actual checks."
    },
    {
      "checked_at": "2026-09-30",
      "evidence_basis": "editorial_adaptation",
      "evidence_date": "2026-09-29",
      "example": "A requested model setting remains a request when the running environment cannot confirm it.",
      "id": "request-versus-observation",
      "kind": "lesson",
      "limits": "No inferred savings or universal agent compatibility is claimed.",
      "mechanism": "Keep the request, observation and missing-data state distinct.",
      "relevance": "Interpreting resource measurements and configuration claims.",
      "status": "demonstrated",
      "summary": "Requested settings and observed runtime or usage are recorded separately.",
      "title": "Separate a request from an observation",
      "tradeoffs": "Unavailable measurements reduce the conclusions that can be drawn."
    }
  ],
  "release_id": "public-9e12c1d8222582cd8d96f75c",
  "schema": "vibe-public-data-v4",
  "theme": "jupiter-v1",
  "visuals": [
    {
      "alt": "Illustration of goals, coding agents, project evidence and a reviewed public publication.",
      "path": "assets/workflow.svg",
      "reviewed_at": "2026-09-30"
    }
  ],
  "website": {
    "capabilities": [
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "id": "coding-agents",
        "limits": "Provider documentation describes the agents. Project settings, tools and permissions still determine a particular run.",
        "references": [
          "codex",
          "claude",
          "delivery-evidence"
        ],
        "status": "provider_documented",
        "summary": "The execution layer plans, edits code and runs tools and checks. VIBE-OS adds the surrounding work and evidence workflow.",
        "title": "Codex + Claude Code"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "accepted_scope",
        "evidence_date": "2026-09-30",
        "id": "phone",
        "limits": "A phone-sized browser test is not a test on a real iPhone. Reading this site does not control a work session.",
        "references": [
          "roadmap"
        ],
        "status": "not_assessed",
        "summary": "The public edition is designed for a phone browser. Real iOS access to a deployed site still needs device and hosting acceptance.",
        "title": "Read on your phone"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "id": "tailscale-access",
        "limits": "Network reachability, service authorization and remote computer control each need their own checks.",
        "references": [
          "tailscale"
        ],
        "status": "provider_documented",
        "summary": "Tailscale documents connecting iOS to a private network. VIBE-OS access through that route has not been accepted in this edition.",
        "title": "Private access with Tailscale"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "id": "remote-access",
        "limits": "A coding session connection does not establish whole-desktop control. No VIBE-OS remote-control acceptance is claimed.",
        "references": [
          "remote"
        ],
        "status": "provider_documented",
        "summary": "Claude Code documents continuing a local session remotely. A VIBE-OS remote-computer workflow has not been assessed here.",
        "title": "Remote session or remote computer?"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "accepted_scope",
        "evidence_date": "2026-09-30",
        "id": "oauth-access",
        "limits": "The protocol definition is documented; provider setup, permissions, revocation and end-to-end acceptance remain to be delivered.",
        "references": [
          "oauth",
          "roadmap"
        ],
        "status": "planned",
        "summary": "OAuth supports delegated access to a service. A reusable VIBE-OS account authorization integration is planned.",
        "title": "Account authorization with OAuth"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "accepted_scope",
        "evidence_date": "2026-09-30",
        "id": "messaging",
        "limits": "No live delivery, recipient acceptance or reply-triggered work is demonstrated by this website.",
        "references": [
          "roadmap"
        ],
        "status": "planned",
        "summary": "Message delivery and authenticated replies are planned integrations.",
        "title": "SMS + WhatsApp"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "accepted_scope",
        "evidence_date": "2026-09-30",
        "id": "learning-pipeline",
        "limits": "Published examples are editorial selections. They do not establish automatic learning or model retraining.",
        "references": [
          "context-evidence",
          "roadmap"
        ],
        "status": "planned",
        "summary": "Curated lessons are available below. Systematic extraction and relevance-led scouting are planned.",
        "title": "Reusable lessons + scouting"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "accepted_scope",
        "evidence_date": "2026-09-30",
        "id": "event-refresh",
        "limits": "An accepted integration needs its own trigger, failure and publication checks.",
        "references": [
          "release-evidence",
          "roadmap"
        ],
        "status": "planned",
        "summary": "Checked static snapshots are supported. Automatically refreshing the website from events is planned.",
        "title": "Event-driven publication"
      }
    ],
    "checked_at": "2026-09-30",
    "comparisons": [
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "editorial_adaptation",
        "evidence_date": "2026-09-29",
        "explanation": "Coordinates agreed work and required checks; code execution belongs to the selected coding agent.",
        "feature": "execution",
        "limits": "Demonstrated local policy, not a guarantee of correct output.",
        "product": "vibe",
        "rating": "Kinda",
        "references": [
          "delivery-evidence"
        ],
        "status": "demonstrated"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "The provider describes a plan, edit, run, observe and repair loop.",
        "feature": "execution",
        "limits": "The cited long-running build is one experiment, not a duration or success guarantee.",
        "product": "codex",
        "rating": "Yes",
        "references": [
          "codex"
        ],
        "status": "provider_documented"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "The overview describes planning changes, editing files, running commands and verifying results.",
        "feature": "execution",
        "limits": "Tool availability and permissions vary by setup; no runtime trial is reported here.",
        "product": "claude",
        "rating": "Yes",
        "references": [
          "claude"
        ],
        "status": "provider_documented"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "A specification progresses through tasks, implementation and convergence using a supported agent.",
        "feature": "execution",
        "limits": "The toolkit supplies workflow; the connected agent performs the coding work.",
        "product": "spec-kit",
        "rating": "Kinda",
        "references": [
          "spec-kit"
        ],
        "status": "provider_documented"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "editorial_adaptation",
        "evidence_date": "2026-09-29",
        "explanation": "Project decisions and delivery evidence are retained for later inspection and curated lessons.",
        "feature": "context",
        "limits": "Automatic cross-project lesson extraction remains planned.",
        "product": "vibe",
        "rating": "Yes",
        "references": [
          "context-evidence"
        ],
        "status": "demonstrated"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "The provider describes working state held in project files, documentation and outputs.",
        "feature": "context",
        "limits": "Persistence alone does not establish that every retained fact is correct or useful.",
        "product": "codex",
        "rating": "Yes",
        "references": [
          "codex"
        ],
        "status": "provider_documented"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "Project instructions and memory support repeated work.",
        "feature": "context",
        "limits": "Context influences a run; it does not guarantee compliance or correctness.",
        "product": "claude",
        "rating": "Yes",
        "references": [
          "claude"
        ],
        "status": "provider_documented"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "Specifications, plans and tasks remain as artifacts used during implementation.",
        "feature": "context",
        "limits": "Artifact quality depends on how the workflow is used and reviewed.",
        "product": "spec-kit",
        "rating": "Yes",
        "references": [
          "spec-kit"
        ],
        "status": "provider_documented"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "local_verification",
        "evidence_date": "2026-09-29",
        "explanation": "Local evidence exercised complete snapshots, unchanged refresh, failure protection and rollback.",
        "feature": "publication",
        "limits": "Local publication evidence does not establish public hosting or service availability.",
        "product": "vibe",
        "rating": "Yes",
        "references": [
          "release-evidence"
        ],
        "status": "demonstrated"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "The cited source does not establish the complete defined publication workflow.",
        "feature": "publication",
        "limits": "This is not a claim that Codex cannot build or support such a workflow.",
        "product": "codex",
        "rating": "Not assessed",
        "references": [
          "codex"
        ],
        "status": "not_assessed"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "The cited source does not establish the complete defined publication workflow.",
        "feature": "publication",
        "limits": "This is not a claim that Claude Code cannot build or support such a workflow.",
        "product": "claude",
        "rating": "Not assessed",
        "references": [
          "claude"
        ],
        "status": "not_assessed"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "evidence_date": "2026-09-30",
        "explanation": "The cited source does not establish the complete defined publication workflow.",
        "feature": "publication",
        "limits": "This is not a claim that the toolkit cannot be extended for publication.",
        "product": "spec-kit",
        "rating": "Not assessed",
        "references": [
          "spec-kit"
        ],
        "status": "not_assessed"
      }
    ],
    "features": [
      {
        "definition": "A supported workflow can change code, run checks and use the result to revise the work.",
        "id": "execution",
        "title": "Execute and verify"
      },
      {
        "definition": "Project artifacts or persistent context carry instructions, decisions or results into later work.",
        "id": "context",
        "title": "Keep reusable context"
      },
      {
        "definition": "The assessed workflow selects approved project evidence and validates an immutable public artifact with rollback.",
        "id": "publication",
        "title": "Publish selected evidence"
      }
    ],
    "products": [
      {
        "id": "vibe",
        "references": [
          "delivery-evidence",
          "release-evidence"
        ],
        "role": "Project delivery + evidence",
        "tags": [
          "Agreed work",
          "Checks",
          "Evidence",
          "Publication"
        ],
        "title": "VIBE-OS"
      },
      {
        "id": "codex",
        "references": [
          "codex"
        ],
        "role": "Coding agent",
        "tags": [
          "Plan",
          "Edit",
          "Test",
          "Working state"
        ],
        "title": "Codex"
      },
      {
        "id": "claude",
        "references": [
          "claude"
        ],
        "role": "Coding agent",
        "tags": [
          "Code",
          "Tools",
          "Instructions",
          "Memory"
        ],
        "title": "Claude Code"
      },
      {
        "id": "spec-kit",
        "references": [
          "spec-kit"
        ],
        "role": "Agent workflow toolkit",
        "tags": [
          "Specify",
          "Plan",
          "Tasks",
          "Implement"
        ],
        "title": "Spec Kit"
      }
    ],
    "references": [
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "id": "codex",
        "title": "OpenAI: a documented coding and verification loop",
        "url": "https://developers.openai.com/blog/run-long-horizon-tasks-with-codex"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "id": "claude",
        "title": "Claude Code: planning, code, tools and project context",
        "url": "https://code.claude.com/docs/en/overview"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "id": "spec-kit",
        "title": "GitHub Spec Kit: specifications through implementation",
        "url": "https://github.com/github/spec-kit"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "id": "tailscale",
        "title": "Tailscale: connect an iOS device",
        "url": "https://tailscale.com/docs/install/ios"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "id": "remote",
        "title": "Claude Code: continue a local session remotely",
        "url": "https://code.claude.com/docs/en/remote-control"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "provider_documentation",
        "id": "oauth",
        "title": "IETF: OAuth 2.0 authorization framework",
        "url": "https://datatracker.ietf.org/doc/html/rfc6749"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "local_verification",
        "id": "release-evidence",
        "title": "Local release checks: dated public evidence",
        "url": "#repeatable-releases"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "editorial_adaptation",
        "id": "delivery-evidence",
        "title": "Delivery policy: an editorial lesson from project evidence",
        "url": "#continue-independent-work"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "editorial_adaptation",
        "id": "context-evidence",
        "title": "Evidence and missing measurements: an editorial lesson",
        "url": "#evidence-stays-dated"
      },
      {
        "checked_at": "2026-09-30",
        "evidence_basis": "accepted_scope",
        "id": "roadmap",
        "title": "Accepted direction and current limits",
        "url": "#roadmap"
      }
    ],
    "schema": "vibe-website-content-v1"
  }
}