Skip to content

Platform Contracts

Contratos formais do modelo de dados do looply. Definem o schema YAML obrigatorio para cada tipo de artefato publicado pelos packs. Garantem consistencia entre packs, hosts e validacao.

Contratos Disponiveis

ContratoSchemaArquivo
Agentlooply/agent@v1platform/contracts/agent.md
Tasklooply/task@v1platform/contracts/task.md
Workflowlooply/workflow@v1platform/contracts/workflow.md
Knowledgelooply/knowledge@v1platform/contracts/knowledge.md
Squadlooply/squad@v1platform/contracts/squad.md

Agent (looply/agent@v1)

Define uma capacidade operacional especializada. Agentes podem declarar context_slots para pre-composicao de prompt.

yaml
schema: looply/agent@v1
name: architect
role: Solution design and technical decision making
execution:
  profile: structured-analysis
  reasoning_effort: medium
  context_budget: medium
  preferred_hosts: [codex, claude]
  model_hint:
    provider: openai
    family: gpt-5
supported_tasks: [create-tech-spec]
knowledge_sources: [../knowledge/architecture-principles.md]
constraints: [Do not invent business rules]
escalation_rules: [Escalate structural ambiguity to pm-analyst]
context_slots:
  - name: constraints
    source: self.constraints
    compose: inline
  - name: knowledge
    source: self.knowledge_sources
    compose: inline
  - name: escalation
    source: self.escalation_rules
    compose: inline
  - name: project_rules
    source: rules
    filter: [architecture-constraints]
    compose: inline
  - name: previous_outputs
    source: stage.inputs
    compose: reference
  - name: feature_context
    source: feature
    compose: reference

context_slots

CampoDescricao
nameIdentificador do slot
sourceOrigem: self.constraints, self.knowledge_sources, self.escalation_rules, rules, stage.inputs, feature
composeinline (looply resolve no sync e inlina no skill) ou reference (host resolve em runtime)
filterLista opcional de categorias para filtrar rules

Task (looply/task@v1)

Instrucoes de trabalho associadas a um agent.

yaml
schema: looply/task@v1
name: implement-api
agent: backend
summary: Implement an API endpoint from the approved tech spec
inputs: [story, tech-spec]
context: [architecture-principles]
outputs: [code-change, api-doc]
templates: [api-template]
checklists: [code-review-checklist]
dependencies: [create-tech-spec]

Workflow (looply/workflow@v1)

Sequencia de stages com gates e handoffs entre agents.

yaml
schema: looply/workflow@v1
name: story-to-production
phase: delivery
orchestrator: delivery-orchestrator
stages:
  - name: technical-design
    task: create-tech-spec
    agent: architect
    outputs: [tech-spec]
gates:
  - name: design-approved
    after_stage: architecture-decision
    owner: architect
    blocks_on_failure: true
handoffs:
  - from: architect
    to: backend
    artifact: tech-spec
command:
  name: story-to-production
  argument_hint: <feature-name> <story-reference> [constraints...]
outputs: [release-plan]

Knowledge (looply/knowledge@v1)

Documento de conhecimento direcionado a agentes especificos.

yaml
schema: looply/knowledge@v1
name: architecture-principles
summary: Stable architectural guidance for engineering agents
audience: [architect, backend]
tags: [architecture, standards]

Squad (looply/squad@v1)

Agrupamento de agentes, tasks, workflows e conhecimento sob um dominio.

yaml
schema: looply/squad@v1
name: architecture-squad
domain: architecture
agents: [architect]
tasks: [create-tech-spec]
workflows: [story-to-production]
knowledge: [architecture-principles]

Artifact-first documentation for looply.