Governed Agentic Computing
FABLE
An Android runtime designed to turn user intent into permitted actions, with explicit approval, recovery and evidence of what actually happened.
The Customer Case
The Opportunity
Delegation is useful when it reduces work without leaving the user uncertain about the outcome. Reliability, integration, permission design and recovery determine which workflows are suitable.
Bring a Customer PerspectiveWhat We Are Building
The Product
FABLE studies digital delegation in which a model may propose a plan while identity, consent and policy determine what may proceed. The present software programme uses stock Android reference devices and preserves evidence of what was actually observed.
- Development Focus
- Governed Agentic Computing
How It Fits Together
The System
A bounded execution loop separates planning from authority, pauses before consequential effects, supports recovery and distinguishes completion from handoff or uncertainty.
Critical Dependencies
- Application integration and permission controls
- Intent interpretation and execution reliability
- Auditability, privacy and recovery mechanisms
System Architecture
How the proposed elements connect.
Intent & Plan
A bounded action plan translates the request into inspectable proposed work.
Authority & Execution
Planning is separated from authority, with explicit approval before consequential effects.
Evidence & Recovery
Execution records distinguish completion, handoff and uncertainty, with recovery for incomplete work.
Conceptual system view. The development questions below set out what needs to be established.
The Next Technical Decisions
Evaluation
Evaluation centres on observed execution: permission boundaries, verified outcomes, recovery and clear handoff when an action cannot be completed.
How is user intent translated into a bounded and inspectable action plan?
Which actions require explicit authorisation, and how are permission boundaries enforced?
How can execution errors, ambiguous requests and incomplete actions be detected and recovered from?
Questions & Answers
FABLE
FAQs
Technical scope, development requirements and ways to contribute.
Ask About FABLEWhat Is FABLE Studying?
FABLE studies governed digital delegation on Android, where a model may propose a plan but identity, consent and policy determine what can proceed. The programme connects intent-driven actions with explicit approval, permission boundaries and evidence of what was actually observed during execution.
Why Use Stock Android Reference Devices?
The present software programme uses stock Android reference devices as a concrete setting for investigating digital delegation. This allows the development questions to be framed around application integration, permission controls and observed execution behaviour, with reliability and recovery assessed within that device context.
How Is Planning Kept Separate from Authority?
The proposed execution loop separates the model’s plan from the identity, consent and policy that determine whether actions may proceed. A proposed action is therefore not itself authority to perform it; evaluation must establish the relevant permission boundaries and how they are enforced.
What Makes an Action Plan Bounded and Inspectable?
An action plan needs a defined relationship to the user’s intent and to the permissions governing execution. FABLE’s evaluation asks how that plan can remain inspectable and limited in scope, so the work addresses what is proposed as well as what may actually proceed.
What Determines When Explicit Approval Is Required?
The proposed loop pauses before consequential effects, while identity, consent and policy determine what can proceed. Development needs to identify the actions requiring explicit authorisation, establish their permission boundaries and examine how those boundaries are enforced within the intended workflow.
Why Distinguish Completion, Handoff and Uncertainty?
The proposed loop distinguishes completed actions from handoffs and uncertain outcomes, with evidence preserving what was actually observed. Evaluation needs to establish how those distinctions are communicated to users, giving them a clear account of the outcome and any question that remains unresolved.
How Are Ambiguous Requests and Incomplete Actions Evaluated?
FABLE’s evaluation includes detecting ambiguous requests, execution errors and incomplete actions, then examining how recovery should work. A suitable workflow needs both a bounded interpretation of intent and a practical response when execution does not produce a clear outcome, with the observed result kept visible.
What Role Does Execution Evidence Play?
The programme preserves evidence of what was actually observed, supporting inspection of actions and their outcomes. That evidence needs to work with privacy and permission controls, so accountability does not depend only on a plan or an assertion that the intended task was completed.
Which Workflows Make a Credible First Application?
A useful application should reduce work while leaving the user clear about the outcome and the authority under which actions occurred. Reliability, application integration, permission design and recovery therefore determine workflow suitability, alongside whether the intent can be expressed as a bounded, inspectable plan.
What Could an Integration or Development Partner Contribute?
A useful partner contribution would clarify the application interfaces, permission boundaries and outcome evidence needed for a particular workflow. That scope can support evaluation of intent interpretation, execution reliability, privacy and recovery, with attention to what happens when actions remain incomplete or uncertain.
Engagement
Work on FABLE
Choose the route that fits your contribution. Your enquiry will carry this venture’s name into the conversation.
Enquire About FABLEBuild the Company
Founders and venture leaders: bring the experience to own the business, product or a critical operating function.
The Founder PathwayExplore an EIR Assignment
Investigate a customer problem, product requirement or development decision. Propose a defined piece of work and a useful outcome.
Discuss an EIR AssignmentContribute a Capability
Research and industry partners: bring a test method, specialist facility, manufacturing process or real customer requirement.
Partnership PathwaysDiscuss Capital
Review the venture’s development plan, evidence, intellectual-property position and financing requirements.
Capital Partner Information