Inside the workflow

Structure around the model work.

Your coding host still reasons and acts. Telic gives that work a deterministic sequence of context, contracts, permissions, evidence, and review.

Stage 01

Start with the request you have

State the problem naturally. Telic preserves the original request and the authority boundary you choose.

InputA rough developer request

OutputImmutable request and mode

Inspectable handoffs

Each stage leaves an artifact.

The next role receives references to bounded inputs instead of relying on an invisible conversation between agents.

Context manifest

Selected repository sources and provenance

Problem frame

Facts, unknowns, scope, and risks

Task contract

Permissions, evidence, and done conditions

Work plan

Ordered actions and stop conditions

Evidence

Observable repository or runtime results

User report

Audited claims and unresolved risk

Authority stays visible

The requested mode follows every handoff.

Telic validates its own artifacts against the active mode and permission contract. Native host actions still remain subject to the host’s sandbox and user approvals.

Missing permission is denial.

report_onlyExplain supplied facts or existing results

plan_onlyCreate a plan without executing it

analyze_onlyInvestigate without changing files or runtime

fix_onlyApply a known correction inside approved scope

analyze_and_fixDiagnose, gate, then fix an evidenced cause

Five logical roles

Clear ownership at every gate.

Roles are responsibilities with strict inputs and outputs. The same host model can perform them serially.

Logical role 01

Scenario author

Frames the repository-specific problem using facts, unknowns, scope, risks, and acceptance criteria.

Creates: Problem frame
Checks: Intent fidelity

01Scenario author

Frames the repository-specific problem using facts, unknowns, scope, risks, and acceptance criteria.

Creates: Problem frame
Checks: Intent fidelity

02Task compiler

Converts the problem frame into an executable contract with permissions, constraints, and evidence requirements.

Creates: Task contract
Checks: Required structure

03Quality controller

Plans the work, checks scope and rules, and owns one bounded remediation when evidence shows a gap.

Creates: Work plan and quality review
Checks: Scope, rules, and completion

04Executor

Investigates, plans, or changes only inside the approved mode while capturing observable evidence.

Creates: Evidence and work result
Checks: Current permission ceiling

05Release auditor

Checks claim-to-evidence links and mode compliance before producing the final user-facing report.

Creates: Release audit and user report
Checks: Evidence and report consistency

Ready to try the flow?

Choose your coding host.

Open installation guide