The Executive Assistant receives CEO requests, distinguishes advice from execution and selects a suitable C-level or member. Both paths have accountable owners; results are cross-checked and significant contributions recorded before handover.
New instructions01The Executive Assistant updates instructions
New CEO instructions may arrive at any step. The Executive Assistant updates the requirements table and informs relevant owners, replaces only conflicting parts, retains effective requirements and continues independent work.
The diagram describes coordination; motion identifies direction, not progress of running work.
The CEO asks a question or assigns a goal. The Executive Assistant retains all requirements, selects suitable help, and consolidates results and the log for handover to the CEO.
The Executive Assistant is the AI focal point directly supporting the CEO: answers within its knowledge, brings in appropriate expertise when needed, and follows assigned work to results. This role uses a shared method independent of any AI provider.
This page explains task assignment and intake in the team. System maps and APIs are separate technical documents owned by the CTO. AI roles follow assigned tasks; diagrams do not start work or replace human decisions.
Profiles and logs are real working data; contribution logs have been stored in the internal database since 02/10/2026. When AI or sessions change, the recipient rereads open requirements, decisions, receipts and process versions to continue the unfinished work correctly.
CLASSIFY REQUESTS AT INTAKE
Two ways to support the CEO
Request advice
The CEO needs an evidence-based answer, analysis or choice before deciding.
The Executive Assistant answers where evidence is sufficient and selects a suitable C-level role or specialist when deeper advice is needed.
The adviser owns the conclusion, sources, trade-offs and uncertainties; the Assistant cross-checks and consolidates them for the CEO.
Record significant advice conclusions by member ID. Questions for understanding or analysis do not automatically authorize product edits or implementation of a proposal.
Handover result The CEO receives an evidence-based answer or proposal with limits; significant contributions retain a traceable history.
Assign work
The CEO requests creation, modification or checking of a specific result within the assigned scope.
The Executive Assistant defines outputs, accountable owners, dependencies and completion criteria, then assigns the right role.
The recipient executes and returns results and evidence; relevant checks and review precede integration.
The Assistant checks all requirements and logs of significant contributions before handover; minor work gets suitable notes. Existing authority carries forward; only new decisions return to the CEO.
Handover result The CEO receives checked results, limits, contribution logs and an owner for any open work.
01FROM REQUEST TO HANDOVER
Coordination steps
Expand or collapse content
Step 01
The CEO asks a question or assigns a goal
The Executive Assistant receives all CEO requirements and priorities and follows them to results.
ResultA list of requirements still in force, with a record of changes.
How to carry it out
The CEO asks for advice or execution, with the desired result and known limits.
The Executive Assistant records every point, including follow-up messages; new instructions replace only prior choices that conflict.
The Executive Assistant distinguishes additions, direction changes, deferrals and progress questions so effective tasks are not lost.
Step 02
The Assistant breaks down and retains all requirements
The Executive Assistant distinguishes advice from execution, separates the required outcomes and maintains a table of requirements still in force.
ResultKnow the required extent and the basis for confirming completion.
How to carry it out
Each requirement has an output, owner, sources to check, dependencies and completion criteria; replaced, deferred or pending parts are marked.
Identify sources and current state to check before concluding or acting. Match checks to the work; do not turn every small edit into new research.
Advice needs evidence-based conclusions and uncertainties; execution needs a deliverable and verification evidence. An analytical question is not authority to edit a product.
Continue when a request is clear and assigned; return to the CEO only for new decisions or missing information that changes the result.
Step 03
The Assistant sends work to the right role
The Executive Assistant handles work within capability or assigns a suitable C-level or member; each task has one accountable owner.
ResultEach task has a clear owner, input and handover point.
How to carry it out
Assign inputs, sources to inspect, scope, owner, completion criteria and return location. The recipient confirms ownership, checks performed and missing inputs.
The COO owns processes and coordinates when assigned; Design owns layout; the CTO owns technical direction. Not every task must pass through COO or CTO, and not every role must be called.
A role transferring work to another retains the same handover information and informs the Assistant. Dispatched work remains tracked to results; a transfer notice does not automatically create a history event.
Step 04
The owner advises or executes
The recipient follows the assigned path, returns an evidence-based result and retains records appropriate to the contribution’s impact.
ResultA concrete result is available for review, with updated impact scope and open work.
How to carry it out
Before concluding or acting, read sources and check the relevant current state; inspect original documents, data or images when they are the basis, rather than relying only on descriptions or excerpts.
For advice, provide evidence-based analysis and choices. For execution, create or edit within scope and keep every affected location consistent.
Distinguish checked facts, assumptions and unverified parts; return outputs with sources, evidence and limits. Qualifying contributions have member-ID records; minor work has brief notes.
When instructions change, adjust affected parts through the coordination focal point; continue independent work that is ready.
Step 05
Review results and recheck unresolved parts
An independent reviewer checks by specialty; the Executive Assistant reconciles comments, uncertainties and the integrated version.
ResultKnow which criteria passed, what remains unresolved and the limits of the check.
How to carry it out
Compare results with requirements, inspected sources and required current state; inspect images/interfaces at actual use size. State intentional differences and unchecked parts.
Reviewers report findings, evidence and how to recheck; unresolved parts return to the owner for fixes or further analysis, without automatic escalation to the CEO for approval.
Advice is checked for sources, assumptions and trade-offs; execution is checked for data, behavior and actual display. Record reviews when findings or conclusions materially support acceptance; repeated checks do not create separate events.
If independent review is unavailable, state self-checks and limits; ask the CEO only when a decision genuinely exceeds the assigned scope.
Step 06
The Assistant reconciles the log and hands over to the CEO
The Executive Assistant compares each requirement with results, records significant contributions and sends the CEO one coherent handover.
ResultThe CEO receives one coherent handover; the recipient knows completed results, saved evidence and next steps for each open task.
How to carry it out
History records only milestones, results or decisions materially affecting products, data, permissions, risk, cost, schedule, organization or processes, including reviews that materially support acceptance.
Transfers, progress reminders, repeated checks and isolated decoration such as portraits, clothes or hair do not create separate events. Minor work gets concise notes or joins a batch with substantive results, retaining traceability.
Reconcile results and qualifying contributions: correct member ID, inspected sources and evidence; reread saved receipts. Assignment or a completion claim does not replace a checked result.
Hand the CEO evidence-based results or proposals, limits and decision points; open work keeps its owner, dependencies and next step. Do not require the CEO to reapprove each authorized action.
When a session or AI changes, preserve open requirements, owners, decisions, result/log receipts and process codes and versions. The recipient rereads and reconciles them before continuing, without relying only on the old session's memory.
02KEEP THE OBJECTIVE CLEAR
Checkpoints
Expand or collapse content
Before starting
The Executive Assistant and recipient identify goals, current authority, sources and state to check; keep facts, assumptions, gaps and result-comparison methods explicit.
When new instructions arrive
The Executive Assistant receives CEO changes and informs relevant roles. The COO updates assignments and dependencies when coordinating; unchanged requirements continue.
When a new decision is needed
Return the precise unclear or out-of-scope point to the Executive Assistant. The Assistant prepares concrete choices for the CEO when needed; ordinary implementation errors return to the implementer.
Before handover
The Executive Assistant checks all results and evidence, reconciles receipts for significant contributions and keeps suitable notes for minor work. Open work has owners, dependencies and next steps for another AI to continue.
The AI focal point supporting the CEO: advises within scope, retains all requirements, selects suitable expertise, reconciles results and logs, and consolidates evidence and uncertainties for handover.
Owns processes, history-recording criteria and the project-management focal point. The Assistant and specialists apply them by actual impact, escalating only difficult cases to the COO; the COO does not approve every small task or filter by keywords. Supports coordination when assigned.
Implements application logic, data and APIs under CTO direction; checks behavior, errors and compatibility and coordinates runtime environments with DevOps.
The CHRO leads the member lifecycle; Admin supports records and handover. Functional managers define needs; technical roles implement approved parts and check together.
Expand or collapse content
Currently available on the website
Profiles, member IDs, assignments and AI[TAI01] role configuration are real files; contribution logs and individual work have been in the internal database since 02/10/2026.
Member IDs retain identity and history; assignments connect people to current positions, with multiple people or positions possible. Assignments do not grant access automatically.
AI[TAI01] role configuration guides work; a tool session is not a website account. Changing sessions or AI[TAI01] does not change member IDs or resume an old process automatically.
Not implemented on the website yet
No account, login, authentication or access-management system exists yet.
Accounts or permissions are not issued or revoked automatically. A website profile does not mean access to the system is available.
The CHRO[OLD07] reads and applies the current onboarding process to the actual case; Admin[OPR14] records needs, the recipient, role and time. Functional managers propose work and permissions for approval by the proper authority.
Create a unique profile and member ID and link approved assignments. Accounts and access are separate, implemented only when the system exists and the request is approved.
HR[OPR13] and QA[TQA01] reconcile actual records; if an account exists, check granted permissions and denied out-of-scope access. Record unavailable parts before handover.
The CHRO[OLD07] confirms the change, effective date and handover recipient; Admin[OPR14] tracks records, and functional managers check both new permissions needed and old permissions no longer needed.
Retain the member ID for the same person after name or role changes. When a holder changes, update assignments and preserve each person’s history; do not transfer old contributions to the replacement.
When permission management exists, implement approved changes and check both new grants and old revocations; do not add permissions while overlooking old ones.
The CHRO[OLD07] confirms the end time; Admin[OPR14] coordinates the handover checklist, and functional managers name recipients for work, data and open issues.
End the current assignment; when accounts or permissions exist, revoke or disable them within the approved scope, including related sessions and access information where applicable.
Retain member IDs and contribution history; reconcile actual handover and revocation results. Deleting identity does not replace permission revocation.
The CHRO[OLD07] leads records, timing and handover; functional managers define work and permission needs. Approval follows assigned authority, not job-title inference.
Coordinate with the CHRO[OLD07] to retain records, checklists, deadlines and receipts. Do not autonomously approve staffing, grant access or use a shared account for a missing member.
Design links between profiles, accounts and permissions and set verification and technical acceptance criteria when this system is implemented.
Backend Engineer
Implement profiles, accounts, data and connected interfaces according to the design and assigned scope; do not decide who receives which permissions autonomously.
DevOps[TOP01] or an authorized administrator grants, configures or revokes permissions in the actual environment under approved requests and returns evidence; adding a profile does not authorize access.
Reread actual results, compare people, roles, effective time and permitted/denied access, and state what could not yet be checked.
Executive Assistant
Track requirements, reconcile results and receipts for qualifying contributions, and hand over completed parts plus owners and next steps for gaps.
Record at handover
Know the process code and version used, CHRO[OLD07] lead, supporting people, approved needs and checks. If a step lacks an owner or authority, refer it to the proper decision-maker; do not use shared accounts or grant access autonomously.
Results distinguish created profiles, implemented accounts/permissions and unavailable systems; confirm only actions supported by reread evidence.
HR[OPR13] leadership does not confer system administration authority. Removing a member card or AI[TAI01] configuration does not prove account and permission revocation.
Log under the correct member ID; retain history and open work through role changes or departure. Creating a profile does not complete the whole onboarding process.