Context before action
Bounds repository context before the host starts semantic work.
Local MCP workflow · Open source
The workflow spine for coding agents.
Turn rough requests into repository-grounded, permission-aware, evidence-linked workflows—without adding another model API.
Prompt Restructure Evaluate Act Verify Report
Explicit authority
Makes scope and permissions inspectable. Missing permission is denied.
Bounded workflow
One contract revision and one shared remediation. No endless loop.
Evidence-linked reporting
Completion claims reference evidence; unavailable checks stay unverified.
See the handoffs
From a vague prompt
to an honest answer.
Telic turns one rough request into a visible sequence of context, requirements, review, evidence, and reporting.
Telic · recommendation-bias · analyze_only
Guided previewUser request
Telic: Is the profession recommendation algorithm flawed, and are the school recommendations appropriate for each profession? Analyze only. Do not change files.
Repository evidencesrc/ranking.ts
Inspectedreturn schools.length === 0 ? [] : [schools[0]];Modeanalyze_only
Files changed0
Runtime claimUnverified
Uses your coding host No Telic cloud Evidence stays linked
The difference
A coding session with a workflow spine.
Telic strengthens high-stakes and ambiguous work without replacing the coding agent you already use.
Typical session
With Telic
Scope can expand silently
Intent and authority become explicit
Context may be guessed
Repository context is selected with bounds
“Done” may be unsupported
Completion claims reference evidence
Review can continue indefinitely
Revision and remediation are bounded
Missing checks invite assumptions
Unknowns remain clearly unverified
Local by design
Control around the model work.
Your coding host performs the semantic work. Telic’s deterministic runtime manages workflow state, artifact validation, and evidence lineage.
Typed handoffs
Every phase creates a strict, inspectable artifact instead of relying on hidden agent memory.
Permission boundaries
Requested mode and effective authority stay visible across the workflow.
Bounded quality loops
One revision and one shared remediation strengthen the work without creating an endless loop.
Local MCP runtime
A local STDIO server stores workflow state and calls no model API of its own.
Start with the request you have