Basar AIEOSby Roel Abasa
The operating framework for accountable AI engineering
Approved intent. Visible work. Human judgment.
Bring an app idea.
Keep direction and delivery in view.
Basar AI Engineering OS is a digital software organization under development. In the planned experience, you describe an app idea to Hermes and clarify a bounded brief: intended users, outcome, constraints and budget. Basar keeps the authoritative project record while Hermes coordinates specialist execution autonomously within approved boundaries. You review the proposed plan, a versioned software candidate and the evidence behind decisions that need your authority.
Product direction — planned operating model; availability depends on the verified release.
For founders, teams and software agencies, the intended value is less review effort, less avoidable rework and clearer handoffs, while retaining direction over the outcome.
Product direction — planned operating model; availability depends on the verified release.
Illustrative model
Hermes assembles temporary teams around each outcome and coordinates their work within approved boundaries. People retain authority over material scope, architecture, risk, budget and release decisions.
Illustrative model
Build from an independently challenged architecture and a human-approved delivery plan. Planned controls would enforce scope, permissions and resource limits, with recovery, revision and exceptions kept accountable.
Illustrative model
Keep versioned requirements, approvals and evidence in the project record. Give each role relevant, bounded context. Retain validated lessons after review and approval; raw chat and worklogs do not become policy.
Illustrative model
Connect accepted outcomes to tests, reviews and artifacts. Attribute usage, cost and budget impact to tasks and projects where verified. Measure cost per accepted outcome; token counts alone are not success.
Product direction — planned operating model; availability depends on the verified release.
Runtime enforcement of the full blueprint-assurance gate remains in development. These commitments describe the intended operating model.
The planned journey starts with an app idea and a bounded brief developed with Hermes. Approved requirements, an independently challenged blueprint and a delivery plan guide the work toward a candidate you can review.
Illustrative model
Clarify the app idea with Hermes through discovery: intended users, outcome, scope, constraints, budget and acceptance criteria. The founder approves the requirements; an initial prompt does not authorize implementation.
Illustrative model
Challenge a fixed blueprint independently of its author. Resolve blocking findings, then obtain human approval of the architecture and delivery plan before implementation starts.
Illustrative model
Hermes coordinates tasks, dependencies, sequencing and recovery within the approved blueprint and plan. Specialists build with continuous security and QA; the founder steers outcomes without managing every agent task.
Illustrative model
Consolidate continuous testing and independent review into current, versioned evidence. Check acceptance criteria, connect findings to corrections and retests, and surface unresolved risks before candidate review.
Illustrative model
Review a versioned candidate with a preview where supported, release notes, evidence and a recovery plan. Request revisions or hold; production release requires explicit human authorization for that candidate.
In the planned lifecycle, preview feedback, operational signals and analytics lead to scoped revisions and new candidates. Lessons are reviewed before becoming shared knowledge; none of these signals silently changes approved scope. Preview availability depends on the verified release.
Product direction — planned operating model; availability depends on the verified release.
Clear responsibilities, coordinated around approved intent.
Approved scope
Evidence and decisions
Clarify founder intent; propose scope and acceptance criteria.
Shape usable, accessible experiences.
Prepare the blueprint for independent challenge.
Build from the approved blueprint and plan.
Test continuously and surface security risks.
Plan reliable delivery; monitor operations and recover safely.
Illustrative role map - not an active agent roster.
Temporary teams are assembled around each outcome. Each role receives only relevant, bounded context. Raw chat and worklogs do not become authoritative memory without review and approval.
The planned operating model
Security and quality are intended to remain active throughout delivery.
Product direction - planned operating model; availability depends on the verified release.
Basar is designed to retain the evidence behind delivery across tasks, sessions and handoffs. A reviewer should be able to establish what was authorized, what changed, what supports completion and what remains unresolved.
Product direction — planned operating model; availability depends on the verified release.
Illustrative accountability trail — not live project, audit, or telemetry data.
Product direction — planned operating model; availability depends on the verified release.
The planned operating view puts project health, delivery phase, outcome progress, budget, aggregate usage and pending decisions first. Drill into agent tasks for their objectives, states, worklogs, evidence and attributable usage.
Planned visibility — no live task, usage, provider, or cost telemetry is shown.
Product direction — planned operating model; availability depends on the verified release.
A credible system needs demonstrated controls and accepted outcomes. Repeated deliveries should show practical value for founders and teams.
Validation goals, not demonstrated outcomes. This page presents no completed delivery or customer-validation evidence.
Capability needs accountability.