Project Orrery

The description states that Project Orrery is a local-first control-plane prototype built using Python and tools like codex and GPT-5.6. It represents work as governed state, not unstructured conversation, and treats planning, execution, review, evidence collection, approvals, and reporting as structured workflow components.

It is described as an operational console, not a chatbot, emphasizing visibility into roles, workflow transitions, findings, approvals, and operator attention. The system enforces separation of responsibilities — for example, planners do not approve their own plans, and builders do not validate their own work.

The architecture is intended to be model- and tool-agnostic, allowing future integration of different AI systems based on capability, cost, privacy, or policy considerations.

Inference The product appears to be a workflow engine for AI-assisted tasks that prioritizes governance over automation speed. It is not a general-purpose AI assistant but a system for managing AI work within defined boundaries.

The author positions Project Orrery as a control plane for AI-enabled work, inspired by mechanical orreries that model planetary systems. The core idea is to enable AI to do more work while remaining subordinate to explicit governance and human authority.

The project evolved from an initial question — “Who is accountable when AI begins performing real organizational work?” — into a prototype that demonstrates governed workflows across planning, building, review, validation, and operator approval.

It claims to address the gap between AI capability and organizational accountability, suggesting that current AI tools lack sufficient oversight mechanisms for enterprise use.

Inference The positioning is focused on governance and control in AI systems. It does not claim to be a general-purpose AI tool or platform but rather a framework for managing AI work within defined roles and controls.

The description states that the project was inspired by cybersecurity, governance, and enterprise technology environments. The author identifies a need in organizations adopting AI assistants, agents, and automation systems where accountability and control are paramount.

It is implied that the target audience includes enterprise users, especially those managing risk-sensitive or high-stakes work involving AI.

There is no explicit mention of specific industries, roles, or organizational sizes. The focus is on governance and accountability, not on a particular customer segment.

Inference The ICP likely includes enterprise teams responsible for cybersecurity, compliance, risk management, or governance — those who require structured control over AI-assisted work.

There is no evidence of a business model or pricing structure in the description. The project is described as a local-first prototype, not a commercial product.

The author does not state whether the system will be offered as SaaS, open-source, or another delivery method. There is no mention of monetization, licensing, or customer acquisition strategies.

Inference No business model or pricing evidence is provided. The project remains in prototype form and has no commercial traction or revenue data.

The system was built as a local-first control-plane prototype, using Python and browser-based interface. It uses tools like codex and GPT-5.6, though the exact model versions are not specified.

It is described as model- and tool-agnostic, with an architecture designed to support future integration of different AI systems based on capability or policy.

The interface is described as an operational console rather than a chatbot, emphasizing workflow state, role separation, and evidence collection.

There is no mention of scalability, deployment infrastructure, or cloud-native capabilities beyond the prototype stage.

Inference The technical approach is experimental and focused on control and governance. It lacks evidence of production-ready architecture or enterprise-scale delivery.

The project is described as a working local-first prototype, but there is no evidence of customer adoption, revenue, or usage metrics.

It was submitted to the OpenAI 2026 hackathon, suggesting it is in early development. There is no mention of funding, partnerships, or product-market fit.

The author notes that the system has evolved from a collection of prompts into a working prototype, but no evidence of iterative improvements, user feedback, or real-world testing is provided.

Inference The project is at an early stage with no demonstrated traction. It remains a prototype and lacks evidence of maturity or commercial viability.

The description does not mention any direct competitors or similar products in the market. It is unclear whether Project Orrery is positioned against other AI workflow tools, governance platforms, or automation systems.

It appears to address a gap in AI governance and accountability, which may overlap with areas such as:

• AI governance platforms
• Workflow automation tools
• Enterprise AI control planes

However, no explicit competitive analysis or differentiation is provided.

Inference No competitive context is evident. The project does not appear to be part of an existing market landscape, nor is it positioned against known competitors.

1. Prototype-only status: The system exists only as a local-first prototype with no evidence of real-world deployment or scalability.
2. No commercial traction: There is no evidence of revenue, customers, or product-market fit.
3. Unproven scalability: The architecture is described as model- and tool-agnostic, but there is no evidence that it can scale beyond a local prototype.
4. Lack of business model clarity: No indication of how the system will be monetized or delivered to users.
5. No user feedback or testing: No mention of real-world use cases, user testing, or iterative improvements.

Inference The project is in early development and lacks commercial viability or enterprise readiness. Risks include lack of traction, scalability issues, and unclear path to market.

1. What specific workflows or use cases have you tested the prototype on?
2. How does the system handle edge cases where AI agents get stuck in loops or fail to make progress?
3. What are your plans for integrating with existing enterprise systems (e.g., source control, cloud platforms)?
4. How do you plan to scale beyond a local prototype to support real operational workloads?
5. Are there any known limitations of the current architecture that would prevent it from being used in production environments?
6. What is the intended delivery model — open-source, SaaS, or another approach?
7. Have you considered how the system will handle multi-tenant environments or cross-organizational workflows?