Examples

Contracts that run in production

These twelve contracts decide the governed actions in µLang Git: claims, pushes, landings, tokens, workflow runs and tool calls. Each was validated, and its digest computed, by ulang-lite 61af4281ed when this page was built.

• ForgeAgentExecutionExecution authority is distinct from assignment and from SDK state/progress.25 clauses · execute_agents
• ForgeAgentManagementAgent management is metadata authority only; it never grants Git, review, check or landing authority.19 clauses · manage_agents
• ForgeClaim12 clauses · grant_claim, release_claim, provision_task, record_event
• ForgeExecutionBudgetMetered plan-run spend: committed plus worst-case reservation stays within the plan's declared limit and a fixed ceiling.7 clauses · budget_execution
• ForgeGitPushA git push is a decision: who may update which refs of this repository, decided before any byte reaches storage.8 clauses · push_refs
• ForgeLanding15 clauses · land, approve_landing, complete_landing
• ForgePlanningAdditive Projects/Issues metadata authority; never grants task or merge authority.11 clauses · manage_planning
• ForgePolicyActivation14 clauses · activate_rules, initialize_forge
• ForgeTaskReconcileOwner-only reconcile of a wedged task: fork credentials revoked and fork head recorded before its claim is released.9 clauses · reconcile_task
• ForgeTokenCustody14 clauses · mint_token, bootstrap_fork_token
• ForgeToolCallEvery call to an upstream MCP tool is one governed decision: catalog-pinned, allow-listed and bounded.14 clauses · call_tool
• ForgeWorkflowRunWorkflow runs are governed: who may start or cancel a run, on which trigger, with which network egress and bounds.17 clauses · run_workflow

To start from

• Deploy approvalThe tutorial contract: two actions, constants, guarantees and prohibitions.ProductionDeploy
• PatternsAllow-lists, ranges, computed values, relations, time windows, rule order.8 patterns
• Expense approvalThe specification's running example.ExpenseApproval