Noetis Life Planning · Personal engine for app builders
Personal Planning Engine for Apps
Builds a realistic weekly or monthly plan from goals and available time.
Answers: "Can an app propose a schedule from goals and available time?" For individuals planning their time.
A proposed plan, not calendar access. It does not book or move events.
Available today
ImplementedImplemented: runs on the shared runtime with supplied material. One bounded development check on 2026-10-12 took 142.1s with 11 model calls and ended "incomplete". That is a development signal, not an evaluation. Customer access is by approved account.
What you send
- Question
- Supplied text material
- Text material up to 150,000 characters per run
What comes back
- Weekly or monthly plan with overload and clashes flagged.
- Findings with the located quote and a support status from claim review
- Release status: released, incomplete with reasons, or failed
- Executed roles, usage and measured cost
Sample
Authored illustration. Written by Encevra to show the workflow. Not customer data and not a recorded model output.
Build my weekly plan.
Work 9 to 5 weekdays plus 1 hour commute each way. Goals: gym 3 times, study Spanish 4 hours, call parents weekly. Kids' practice Tue and Thu 6 to 7:30. Want 8 hours of sleep.
- A proposed weekly plan within the stated hours
- Goals that do not fit and why
- Tradeoffs for the user to choose between
The real response shape is documented in the API reference.
How the workflow operates
Each role is a responsibility in the workflow, served by a third party language model. More roles are not automatically better; depth and routing decide which run.
Built with
Models this engine uses: OpenAI (GPT), Anthropic (Claude). Specialists run on OpenAI models and the claim review and final brief on Anthropic models. If a provider has a temporary failure, the step can fall back to an OpenAI model, and the run records that.
Priority Analyst
Clarify and rank the goals the person states.
Capacity Planner
Total the time actually available from supplied commitments.
Schedule Builder
Propose a plan that fits the measured capacity.
Conflict Reviewer
Identify overload, clashes and unrealistic blocks.
Evidence and deployment
Evidence
This engine reads the text you send in the request. Each released finding carries the exact quote and its character span in that text, located mechanically before release. Quotes that cannot be located are labelled Insufficient evidence and never shown as source verified. Interpretation is reviewed as a separate step, and gaps such as a missing clause describe what was searched instead of citing text that is not there.
Deployment
Runs on Encevra hosted infrastructure using the third party models listed above. Every model call and fallback is checked against the deployment policy first. Private cloud and air-gapped deployment are planned; discuss deployment requirements.
What it does not handle
- Calendar writes (need a separately authorized integration)
- Calendar write access is not available: Not built. Plans are returned as text only.
- Uses only supplied material. No freshness guarantee beyond the documents provided.
- Required for every output during trials.
How to integrate
Send "engine": "life-planning" with your question and material from your server. Keys stay server side.
How to evaluate it
No published result for this workflow yet. Build a small answer key from your own work and compare against a strong single model baseline. See the evaluation checklist and method.
Cost and rights: pricing and licensing. Showing outputs to your own customers needs a written agreement.
Related engines
Content reviewed 2026-10-12 by the Encevra engine team. Engine version 0.1.0 on noetis-core-1.