<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tetonic Engine on Tetonic</title><link>https://tetonic.ai/</link><description>Recent content in Tetonic Engine on Tetonic</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 24 Sep 2026 12:00:00 -0400</lastBuildDate><atom:link href="https://tetonic.ai/index.xml" rel="self" type="application/rss+xml"/><item><title>Architecture</title><link>https://tetonic.ai/docs/engine/architecture/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/docs/engine/architecture/</guid><description>&lt;p&gt;The engine separates how work is requested, coordinated, executed, remembered, and connected to models.&lt;/p&gt;
&lt;h2 id="applications-and-interfaces"&gt;Applications and interfaces&lt;/h2&gt;
&lt;p&gt;Applications direct the runtime through interfaces. The source tree includes terminal and daemon interfaces. Existing executable names such as &lt;code&gt;lokai&lt;/code&gt; and &lt;code&gt;lokaid&lt;/code&gt; may still appear in build instructions; they are interfaces into the engine, not separate product lines.&lt;/p&gt;
&lt;h2 id="coordination-and-execution"&gt;Coordination and execution&lt;/h2&gt;
&lt;p&gt;Coordination manages work across agents and execution resources. The runtime carries out agent work within configured tool and policy boundaries. Keeping these responsibilities separate is central to the distributed design.&lt;/p&gt;</description></item><item><title>The Village</title><link>https://tetonic.ai/experiments/the-village/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/experiments/the-village/</guid><description>&lt;p&gt;The Village is an experiment, not a guarantee of production behavior or engine scale.&lt;/p&gt;</description></item><item><title>Execution &amp; permissions</title><link>https://tetonic.ai/docs/engine/permissions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/docs/engine/permissions/</guid><description>&lt;p&gt;Autonomous work needs explicit boundaries. The engine&amp;rsquo;s approach is to put those boundaries in the execution path.&lt;/p&gt;
&lt;h2 id="tool-actions"&gt;Tool actions&lt;/h2&gt;
&lt;p&gt;Shell commands, file writes, and network access are distinct kinds of action. Configure the permissions appropriate to each workload instead of treating all tool calls as equivalent.&lt;/p&gt;
&lt;h2 id="policy-decisions"&gt;Policy decisions&lt;/h2&gt;
&lt;p&gt;Policy can allow, ask, or deny an action. Approval is part of the execution model; a permitted action does not necessarily require a new dialog each time.&lt;/p&gt;</description></item><item><title>Distributed operation</title><link>https://tetonic.ai/docs/engine/distribution/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/docs/engine/distribution/</guid><description>&lt;p&gt;The Tetonic Engine is designed as distributed infrastructure. Growing beyond one machine should not require a different product.&lt;/p&gt;
&lt;h2 id="begin-with-responsibilities"&gt;Begin with responsibilities&lt;/h2&gt;
&lt;p&gt;An application supplies intent and context. Coordination organizes work. Execution resources carry it out, and the state layer preserves the record. Inference supplies model responses.&lt;/p&gt;
&lt;p&gt;These roles may be close together on one machine or separated across infrastructure. The homepage diagram illustrates these roles; it is not a live cluster monitor or a deployment command.&lt;/p&gt;</description></item><item><title>Explore the source</title><link>https://tetonic.ai/docs/engine/development/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/docs/engine/development/</guid><description>&lt;p&gt;The &lt;a href="https://github.com/tetonic-labs/tetonic"&gt;Tetonic repository&lt;/a&gt; is the starting point for the engine implementation.&lt;/p&gt;
&lt;h2 id="build-instructions"&gt;Build instructions&lt;/h2&gt;
&lt;p&gt;Follow the README and contributor instructions for the revision you check out. They describe the supported build environment and available interfaces. This site does not publish a separate engine installer.&lt;/p&gt;
&lt;h2 id="existing-component-names"&gt;Existing component names&lt;/h2&gt;
&lt;p&gt;The codebase may still use names such as &lt;code&gt;lokai&lt;/code&gt;, &lt;code&gt;lokaid&lt;/code&gt;, and &lt;code&gt;mantle&lt;/code&gt;. Those names identify existing interfaces or internal components. The product is the Tetonic Engine.&lt;/p&gt;</description></item><item><title>One engine. A broader foundation.</title><link>https://tetonic.ai/blog/one-engine/</link><pubDate>Thu, 24 Sep 2026 12:00:00 -0400</pubDate><guid>https://tetonic.ai/blog/one-engine/</guid><description>&lt;p&gt;Tetonic is moving to one product: &lt;strong&gt;the Tetonic Engine&lt;/strong&gt;, a distributed agent runtime engine.&lt;/p&gt;
&lt;p&gt;The work is infrastructure. Agent execution, coordination, state, and model access need to fit together as a system that can grow across machines.&lt;/p&gt;
&lt;p&gt;Applications and interfaces can build on that foundation. They no longer define separate product lines.&lt;/p&gt;
&lt;p&gt;Scale is the direction we are designing for. It has to be demonstrated through the workloads, deployment topologies, and failure cases the engine is tested against.&lt;/p&gt;</description></item><item><title>Owner-operated agent software</title><link>https://tetonic.ai/blog/owner-operated/</link><pubDate>Wed, 02 Sep 2026 12:00:00 -0400</pubDate><guid>https://tetonic.ai/blog/owner-operated/</guid><description>&lt;p&gt;Tetonic Labs LLC builds owner-operated agent software. The work runs on hardware the customer owns. Tetonic is not a hosted agent service and not a single app.&lt;/p&gt;
&lt;p&gt;Lokai is the first product: a local coding assistant. Later products will follow the same rule: your machines, your data.&lt;/p&gt;
&lt;p&gt;The company is the rule. The products are applications of it.&lt;/p&gt;</description></item><item><title>An agent runtime you operate</title><link>https://tetonic.ai/blog/an-agent-runtime/</link><pubDate>Wed, 02 Sep 2026 11:00:00 -0400</pubDate><guid>https://tetonic.ai/blog/an-agent-runtime/</guid><description>&lt;p&gt;Today Lokai is a terminal program (lokai) and a background service (lokaid) that an editor can talk to. You can run it as a one-shot task or as an interactive session.&lt;/p&gt;
&lt;p&gt;If you have more than one machine, you can add machines you trust and use them to run the models. That is still your hardware, not a fleet we host.&lt;/p&gt;
&lt;p&gt;The longer aim is software you operate yourself: start work, limit it, tool it, watch it, cancel it, and keep a durable record on your data. The coding assistant is built on that.&lt;/p&gt;</description></item><item><title>Software work, not only chat</title><link>https://tetonic.ai/blog/software-work/</link><pubDate>Wed, 02 Sep 2026 10:00:00 -0400</pubDate><guid>https://tetonic.ai/blog/software-work/</guid><description>&lt;p&gt;Lokai is for software work, not only chat. It can answer questions, inspect a codebase, search, plan, edit, test, debug, and review.&lt;/p&gt;
&lt;p&gt;It can also do a turn that never touches a file.&lt;/p&gt;
&lt;p&gt;Dangerous actions wait. Shell and network go through approval. Network access is denied unless you allow it. Writes go through policy, which can allow, ask, or deny.&lt;/p&gt;</description></item><item><title>Cookies</title><link>https://tetonic.ai/cookies/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/cookies/</guid><description>&lt;p&gt;This site uses as little cookie storage as it can.&lt;/p&gt;
&lt;h2 id="strictly-necessary"&gt;Strictly necessary&lt;/h2&gt;
&lt;p&gt;&lt;code&gt;consent_posture&lt;/code&gt; is set by the server. It tells the consent script whether this visit should opt in (ask first) or opt out (load until you decline). It is not a marketing cookie.&lt;/p&gt;
&lt;p&gt;Your choice is stored in &lt;code&gt;localStorage&lt;/code&gt; under &lt;code&gt;tetonic_consent&lt;/code&gt; so the banner does not reappear on every page.&lt;/p&gt;
&lt;h2 id="analytics"&gt;Analytics&lt;/h2&gt;
&lt;p&gt;A cookieless analytics script, when configured, loads for every visit and does not set cookies.&lt;/p&gt;</description></item><item><title>Owner-operated</title><link>https://tetonic.ai/resources/owner-operated/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/resources/owner-operated/</guid><description>&lt;p&gt;The Tetonic Engine is designed to run on infrastructure you control. Decide where work executes, which models it can reach, and which tool actions it may take.&lt;/p&gt;
&lt;p&gt;This remains the goal as work moves from a machine to distributed infrastructure. Read &lt;a href="https://tetonic.ai/docs/engine/distribution/"&gt;Distributed operation&lt;/a&gt; for the design considerations.&lt;/p&gt;</description></item><item><title>Ownership</title><link>https://tetonic.ai/resources/ownership/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/resources/ownership/</guid><description>&lt;p&gt;Infrastructure choices determine where code, context, history, and artifacts live. The Tetonic Engine is designed to keep those choices with the operator.&lt;/p&gt;
&lt;p&gt;Review model endpoints, access policies, and state storage as part of your deployment. Read our &lt;a href="https://tetonic.ai/trust/"&gt;operational principles&lt;/a&gt; and &lt;a href="https://tetonic.ai/docs/engine/permissions/"&gt;execution guide&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Privacy</title><link>https://tetonic.ai/privacy/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/privacy/</guid><description>&lt;p&gt;Tetonic Labs LLC operates this site at tetonic.ai.&lt;/p&gt;
&lt;h2 id="what-we-collect"&gt;What we collect&lt;/h2&gt;
&lt;p&gt;If you use the contact form, we receive the address you give, the optional name, the message, and any product or system fields the form includes. We use that to reply.&lt;/p&gt;
&lt;p&gt;The form is posted to FormSubmit, which delivers the message to &lt;a href="mailto:hello@tetonic.ai"&gt;hello@tetonic.ai&lt;/a&gt;. FormSubmit is not embedded on this page. The first message to an address requires a confirmation from that inbox.&lt;/p&gt;</description></item><item><title>Sent</title><link>https://tetonic.ai/contact/sent/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/contact/sent/</guid><description>&lt;p&gt;We will write back at the address you used.&lt;/p&gt;</description></item><item><title>Terms</title><link>https://tetonic.ai/terms/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tetonic.ai/terms/</guid><description>&lt;p&gt;These terms apply to tetonic.ai, operated by Tetonic Labs LLC. They do not license product software. Download and pricing are not on this site yet.&lt;/p&gt;
&lt;h2 id="use"&gt;Use&lt;/h2&gt;
&lt;p&gt;You may read this site for lawful purposes. Do not attempt to disrupt it or scrape it in a way that harms the service.&lt;/p&gt;
&lt;h2 id="content"&gt;Content&lt;/h2&gt;
&lt;p&gt;Material on this site is provided as published. It may change. It is not professional advice.&lt;/p&gt;
&lt;h2 id="disclaimer"&gt;Disclaimer&lt;/h2&gt;
&lt;p&gt;The site is provided as is. Tetonic Labs LLC is not liable for damages arising from use of the site, to the extent the law allows.&lt;/p&gt;</description></item></channel></rss>