Skip to main content

Getting Started with pvot

Here are the top five things a developer should know when getting started with Infrastream and pvot.

1. Declarative, Manifest-Driven Architecture​

Everything in Infrastream — from organizations and environments to databases and workloads — is defined declaratively via YAML/JSON manifests stored in your version-controlled Git repository. The engine maintains your live infrastructure state directly from these definitions.

Action: Inspecting manifest configurations, schemas, and resource definitions.

Example prompts:

  • "What is the schema for a Database manifest?"
  • "Show me the manifest details and raw YAML for the staging-api project."
  • "Search active manifest kinds available to author in our tenant."

2. Git-Native PR Workflow with Pre-Commit Validation​

Infrastream uses GitHub pull requests for all infrastructure changes. Proposed manifest changes are automatically linted (infra-lint) before committing, ensuring syntax, schema correctness, and parent-child relationship validity before landing on main.

Action: Authoring, linting, creating, or reviewing infrastructure pull requests.

Example prompts:

  • "Create a PR to add a Redis cache manifest to our production environment."
  • "Lint these proposed YAML files against our current repo before we open a PR."
  • "List all open infrastructure pull requests and summarize PR #14."

3. Infrastream & Specialized Squad Orchestration​

You can ask pvot directly to inspect live resources, run diagnostics, track CD deployments, or author manifest PRs. For broader needs, pvot can delegate directly to specialized squads:

  • Planning Squad — architectural design, migration planning, and consensus building.
  • Engineering Squad — code implementation, testing, and debugging.

Action: Tasking pvot directly, or delegating complex design or code tasks to squads.

Example prompts:

  • Planning Squad: "Design a multi-region failover plan for our microservices pipeline."
  • Engineering Squad: "Help me write and debug a Go service to publish metrics to Cloud Logging."
  • pvot: "Summarize our current repository topology and list unassigned resources."

4. Continuous Delivery & Gate Approvals​

Infrastream natively handles release and pre-release deployments across environments. You can track deployment pipelines, review changelogs, manage gate approvals, and view per-run mutation histories directly from the platform.

Action: Tracking deployment pipelines, stage statuses, gate approvals, and changelogs.

Example prompts:

  • "List our recent CD deployments and show any that are awaiting approval."
  • "What commits and changes were included in deployment dep-8492?"
  • "Show the stage history and error log for our latest release deployment."

5. Full State Visibility & Audit Logging​

Infrastream builds a live state graph mapping parent-to-child relationships (OWNS) and resource dependencies (USES/REQUIRES). Every change, state delta, and engine execution is logged with complete auditability, letting you trace resource evolution over time.

Action: Searching live graph states, tracing resource dependencies, and reviewing execution audits.

Example prompts:

  • "Show me the dependency graph connecting our environments and services."
  • "What physical cloud resources were created or modified in the latest engine run?"
  • "Search active states for any resources matching auth-service."