Project portfolio

Brief descriptions, recorded status and one next action for each workstream.

Use status to choose the next step, not to infer a launch.“Review needed” means an acceptance, owner or evidence decision remains. “Validate” means prepared research or a test kit exists; it does not mean demand is proven. Open a project for source paths and limits.

This week · 5–11 October

A suggested starting shortlist. Change the projects and hours to match your actual availability.

Proposed focus

Clear a gate. Finish an output.

Start with the RheMind hosted-CI blocker, one complete Manna review and Pefiwa’s physical-device verification.

03

Add another project

Changes here affect your plan only. A tick records your own task completion, without changing the evidence-based project status.

October → December

Suggested sequencing, not delivery promises. Use the selectors to move a project between months, or open “Later” to pull one forward.

Laterno implied commitment · open to schedule one

Archivedset aside · excluded from counts and plans · pick another slot to restore

Year-end outcome · choose a small finish lineRheMind’s late-December launch is a recorded target, not an agreed commitment. Decide the minimum accepted App/CMS scope, required release evidence and actual weekly capacity before putting a launch date in the calendar.

Commercial focus · one experiment at a timeApp Ideas, Dweise, Automate and AI Biz Ideas overlap in purpose. Select one test with a buyer, offer and measurable response; revisit the next idea after the result. Mark the rest as Later to protect delivery time.

Older evidence needs a short state refresh before work resumes. A quiet workspace may be delivered, deliberately paused or simply under-documented; it is not automatically abandoned.

Your year-end priorities

How to read this review

A local evidence snapshot taken on 5 October 2026.

What was reviewed

Freshness: dates refer to the latest selected evidence, not the day the project was completed. Older than September is labelled “Older evidence”. Folder modification dates alone are not completion proof.

Grouping: local aliases, documentation and implementation copies are grouped. Distinct workstreams inside RheMind and Enact stay separate. Shared and thin workspaces remain visible under Infrastructure or Reference.

Your plan: selectors, hours, notes and ticks are local planning choices. They do not update project repositories, approvals, trackers, chats or external schedules. The source statuses remain fixed to this snapshot. Deleting a project removes it from this planner only; source folders are never touched.

Status key

Why there is no overall completion percentageProjects have different scopes, and some have research outputs but no approved build. Counts and explicit gates are more useful than a fabricated percentage.

Workspace coverage and local aliases

Your projects, at a glance.