duranteOSPTAccess A SYSTEM FOR WORKING WITH AI · A PRODUCT BY DURANTE
DuranteOS is the system Durante uses to track requests, coordinate AI agents and bring deliveries back for review. Decisions and history stay connected to the work.
In use at Durante · in development · restricted access
Altyaa is in production. AdCore Turbo is evolving, with another operator delivering with DuranteOS. Explore the outcomes below.
01 / WHAT IS DURANTEOS
A request arrives in one conversation. A decision stays in another. The delivery goes into a repository. When something changes, someone has to put it all together again.
DuranteOS connects the work to its context, rules, execution and results. It is the system Durante uses to organize work with AI across multiple projects.
A conversation can help prepare an answer or perform a task. A delivery also needs an agreed scope, follow-up and someone responsible for checking the result. Durante takes responsibility for the agreed work; DuranteOS organizes the context, execution and records that support that operation.
Start with one concrete request. Agree on what needs to be delivered and what you will review. The walkthrough below shows how we follow a real task in our own operation.
Goals, priorities, boundaries and decisions.
Context · work · rules · evidence · memory
Research, write, build and check the work.
A map of responsibilities. DuranteOS uses AI; it is not a new language model.
The system also supports research, preparing materials and organizing operations. Adopting it in another company requires defining scope, connections and responsibilities.
02 / ONE TASK, FROM REQUEST TO MEMORY
A real request: follow the agents without going back to the terminal. Follow task #2882 · Timeline through Pulse, the DuranteOS dashboard.
01 / BOARD
Task #2882 asks for a Timeline to follow the agents as a feed. Its card keeps the goal and follow-up date visible on the board.
Current Pulse · light theme
Captured October 16, 2026
02 / RECORD
Every task keeps a living record. This one holds the options considered and what done means: newest updates first, what waits on you pinned on top, read-only, readable on a phone.
From task #2882's record
Reworded for this page
DONE MEANS
Chosen: a read-only page over records that already exist, with no new store. Set aside: a history column on an existing page.
03 / DELIVERY
The delivery is the Timeline itself. It brings agent updates into a feed. This is the current interface, which has evolved since the first version.
Current Pulse · light theme
Captured October 16, 2026
04 / MEMORY
Searching for 2882 in Cortex, Pulse's memory area, returns 40 results across six categories: the task's original record and the work that followed it. The next step can start from decisions already made.
Current Pulse · light theme
Captured October 16, 2026
The first Timeline was delivered and checked on October 6, 2026. The task also called for measuring its effect on requests for progress updates; we do not present that impact as established. The three screenshots in this walkthrough were captured from the installed interface on October 16, in light theme. They are real crops; where they showed internal labels or private records, the text is covered with solid blocks, never rewritten. Step 02 shows no screenshot: its record is private, so its criteria are reworded.
Open the delivery record ↗03 / WHAT'S IN THE SYSTEM
In Pulse, the DuranteOS dashboard, every task has a place: ready to start, in progress, blocked or in review. See the next step without reconstructing the conversation.
Goals, projects and rules provide a starting point for the work. A new task can build on what has already been defined.
The goal structure and context loading inform the primary tool. External agents receive instructions scoped to the work, and rules on what they may write and publish.
Built on: TELOS · session context · task instructionsRequests become work tracked by project, priority and state. The dashboard helps locate deliveries, blockers and pending decisions.
The work board uses task records. The operator's brief brings together pending decisions, urgent and overdue items, today's focus and completed deliveries.
Built on: Work · Pulse · operator briefWork can be distributed across tools and agents. Scope, instructions and remaining work help carry context between sessions.
The system assigns tasks, records who is working and prepares context for a successor session. Controls vary by tool; compatibility with every model is not promised.
Built on: Work · session status · context handoffsThe work defines criteria and records checks. Tests, code review and browser inspection help show what was actually verified.
Work records connect criteria to evidence. The delivery process includes review by another model. A local check, an approved change and production operation remain distinct states.
Built on: work records · reviews · delivery checksDecisions, research and lessons can be retrieved with their dates and sources. That history helps resume an investigation or prepare the next change.
Memory supports search, a timeline and reading individual records. Files and structured records keep information available. Items can be exported; that is not the same as a complete, automatic migration of an installation.
Built on: Cortex · search · sources · timelineRules guide actions and define what needs a person. Corrections can become instructions for future work.
The primary tool has automatic checks at points in the workflow. Other tools receive their own execution rules. Configuration and supervision are required: this does not guarantee that any action in any tool will be blocked automatically.
Built on: operating rules · checks · recorded correctionsDuranteOS is in use at Durante. Product access remains restricted.
04 / FROM THE SYSTEM TO THE WORLD
Altyaa and AdCore Turbo are concrete outcomes of work with DuranteOS: a production SaaS and a platform undergoing migration and evolution. Another operator is leading the AdCore Turbo deliveries with the system.
PRODUCT IN PRODUCTION
Accounts, organizations, subscriptions and agents for digital presence and reputation. Users review recommendations and actions.
See the delivery on Durante's site ↗
Accounts, organizations, subscriptions and connected profiles support continued use.
Agents for Google, Facebook, Instagram and TikTok prepare analyses and recommendations.
Users review and can edit what was prepared before approving it.
ADCORE TURBO · MIGRATION AND EVOLUTION
AdCore Turbo’s evolution spans catalog management, digital assets, integrations and product-data distribution. Another operator is delivering this work with DuranteOS.
The system is also being used to deliver software by an operator other than the founder. AdCore Turbo’s migration and optimization remain ongoing.
These are examples of products and features delivered with DuranteOS. They do not, by themselves, establish time, cost or revenue gains, or adoption of DuranteOS at scale.
05 / MORE EXAMPLES
The same system also supports decisions, investigations and preparing materials. Explore two real examples, edited to protect private information.
Source: decision receipt and follow-up records, October 14, 2026.
Open edited record ↗FROM DELIVERY TO THE NEXT STEP
The delivery was more than a reply in a conversation. The receipt showed what entered the work queue, what was deferred and what would not proceed. New tasks stayed queued; this decision did not execute them.
This receipt confirms how the choices were routed. It is not proof that the tasks were completed.
An editorial presentation, not an interface screenshot. The original files remain private.
06 / SOFTWARE AS SELF
This is the direction we are building toward: software shaped by your intent that evolves with your experience.
At Durante, people set direction and remain accountable for decisions. Agents take part in execution. DuranteOS connects that work to context, rules and what has already been learned.
Meet DuranteGoals and boundaries come before execution.
Decisions and evidence help explain the path.
What was learned informs the next step.
07 / WHERE THE PRODUCT STANDS
DuranteOS is in use in Durante's operations and remains in development. Access is restricted: there is no public installation or opening date, and the waiting list is open. Join the waiting list ↗
Talk to LucasThe offering brings together context and rules, work tracking, agent execution and searchable memory. Configuration depends on each operation's projects, information sources and permissions. Today this still requires technical work; there is no self-service deployment package for any company.
The system stores files and records on the installation's infrastructure. That does not mean all execution is local: an external model or service may receive the context needed for a task. Providers, permissions and data boundaries must be defined during configuration.
Simple onboarding, role-specific configuration and a clear interface for nontechnical users. Time, cost and quality improvements need to be measured case by case; the examples on this page do not establish general savings or unsupervised operation.
Access is closed. This page introduces the product and work done with it; it offers no download. Joining the waiting list promises no date and no access.
Durante is the company you work with: people agree on the scope, take responsibility for delivery and review the result with you. DuranteOS is its product for connecting the request, context, agents, decisions and evidence. The examples above show work delivered with that system, including by another operator.
DuranteOS originates in LifeOS, by Daniel Miessler. Durante's product applies that foundation to its own working context, with execution, review and continuity practices. We acknowledge that origin without treating the entire foundation as our own creation.
The diagrams explain the approach. Work, Timeline and Cortex captures come from Pulse as installed on October 16, 2026. They are real crops; internal labels and private records are covered with solid blocks or cropped out, and step 02 rewords a private record instead of showing it. The delivery record retains checks from October 6; images show the current interface. The Altyaa capture shows a real public page. The AdCore Turbo approvals screen has private details permanently removed. The cards and linked records are editorial adaptations of real records, without private names, messages or identifiers. No simulation is presented as live execution.
