Authoring Guide

rescile’s authoring model consists of four primary development workflows, each unlocking different aspects of your dependency graph.

flowchart LR
    subgraph W["Data plane: data directory + modules"]
        assets["Assets (CSV)<br/>ground truth"]
        models["Models (TOML)<br/>blueprints"]
        policies["Policies (TOML)<br/>governance rules"]
        outputs["Outputs (TOML)<br/>artifact templates"]
        actions["Actions (TOML)<br/>declarative tasks"]
    end

    assets -- "1. raw resources" --> resgraph[("Graph")]
    models -- "2. create, connect, propagate" --> resgraph
    policies -- "3. mutate, enrich, attach controls" --> resgraph
    resgraph -- "4. query and generate" --> outputs
    outputs -- "artifacts: JSON, scripts, Terraform, reports" --> ext["External systems"]
    actions -. "5. trigger via REST or MCP" .-> runner["Runner (sandboxed execution)"]
    runner -. "apply / remediate" .-> ext

Each phase builds on the previous one: models turn facts into a connected graph, policies mutate that graph to enforce standards, outputs query the governed graph to produce artifacts, and actions execute business logic against the world.

Models

Transform raw assets into a rich, interconnected dependency graph using declarative TOML models. Create derived resources, propagate data across connections, and join information from different systems.

Policies

Enforce governance and security policies automatically. Apply organizational standards, insert network intermediaries, and ensure compliance by design.

Outputs

Generate actionable artifacts from your completed graph—from structured data like JSON and YAML, to executable scripts, Terraform configurations, Kubernetes manifests, and comprehensive compliance reports.

Actions

Define securely sandboxed, trigger-based automation. Expose your infrastructure intent to AI Agents via the MCP Server or directly execute business logic through standardized APIs.

Design Patterns

Apply field-tested patterns for assets, relations, lifecycles, actions, and dashboards—learned from production modules and distilled into reusable guidance with links into the reference docs. See Design Patterns.