PROCESS MANAGEMENT · COO

Process catalog

Look up each studio process's code, version, scope and owner.

Catalog version1.4.0

COO maintains the shared catalog and tracks changes. Each process has a specialist lead; its code stays the same when its name changes, while its version records content changes.

Status here describes the process's scope of use. Results of each execution are recorded separately in work history; having documentation does not mean the work is complete or an account has been issued.

Team coordination

QT0001Process version3.0.0

Team coordination · Guidance available

Coordinate task intake and handover

Retain all CEO requirements, assign the right expertise, check results and record significant contributions against COO criteria before handover.

Lead COO

Scope and required outcomes

When to apply: The CEO requests advice, assigns execution or updates an ongoing task.
Required outcomes: Evidence-based results; open requirements have an owner and a next step.
Currently in use: Six-step guidance, criteria with work-log examples and an API writing mechanism exist; people and AI apply them to each assigned task.

This is not an automated orchestrator or a running progress board.

QT0002Process version1.2.0

Team coordination · Guidance available

Member onboarding

The CHRO leads; Admin supports records and handover. Creating a profile is separate from issuing accounts and permissions.

Lead CHRO

Scope and required outcomes

When to apply: An assigned request exists to add a member to the team.
Required outcomes: Member identity, assignment and data are reconciled; any part not ready to proceed is explicitly recorded.
Currently in use: Profiles, member IDs, assignments and AI role configuration are in the website source; contribution logs and individual work have been in the internal database since 02/10/2026. Adding a member must update both consistently; the CHRO reads and applies the process before each onboarding.

Automated accounts, login and permission assignment are not yet available.
A created profile does not prove completed permission assignment or an employment relationship.

QT0003Process version1.0.0

Team coordination · Guidance available

Role or permission changes

Record the change needed, retain identity and history, and check both permissions to add and old permissions to remove.

Lead CHRO

Scope and required outcomes

When to apply: A change of name, duties, position, holder or access needs.
Required outcomes: The new assignment has evidence and an effective time; handover and permission changes reflect the extent actually checked.
Currently in use: Assignments and names can be updated in the current source; Admin coordinates input and result tracking.

Changing an assignment does not automatically change system permissions.
A member retains their ID after a name, model or tool change; a replacement does not inherit the previous person’s history.

QT0004Process version1.0.0

Team coordination · Guidance available

Team departure or end of assignment

Confirm completion, hand over work and check revocation in systems that actually exist.

Lead CHRO

Scope and required outcomes

When to apply: A decision ends a position assignment or team membership.
Required outcomes: Open work has a recipient; IDs and history remain; revoked permissions are distinguished from pending revocations.
Currently in use: Guidance exists for ending assignments and preserving records; Admin coordinates the handover checklist.

The website does not yet support disabling accounts or login sessions.
Hiding a card or stopping an AI configuration does not prove permissions were revoked.

QT0005Process version1.0.0

Team coordination · Guidance available

Manage the process catalog

Assign stable codes and retain each process’s version, functional owner, status and sources.

Lead COO

Scope and required outcomes

Record the change request, goals and sources; distinguish a new process from an edit to an existing one.
Identify the functional owner and application context; reconcile inputs, outputs and current authority.
Keep the code of the process being edited; for a new process, assign an unused code and check for duplicates.
Assess the version increase, status, current scope and content sources.
Synchronize references and display locations; review and check codes, owners, versions and links.
Record results and evidence by member; reread the receipt and hand the current version to the functional owner.

When to apply: A new process or a change to an existing process’s goals, steps, functional owner, sources or status.
Required outcomes: The catalog and its consumers reference the same correct code, version and content; change history is retained.
Currently in use: The catalog is managed through typed source files and maintenance guidance; the COO coordinates, and functional owners confirm the content.

The catalog page is a reference; online editing or approval is not yet available.
Do not issue a new code merely because a process is renamed, a page moves or another diagram is drawn.

QT0014Process version1.0.0

Team coordination · Implemented within the stated scope

Prepare an application draft

Choose a position and prepare application information as a draft retained by the user.

Lead CHRO

Scope and required outcomes

When to apply: An interested person opens the application page from a position or chooses their specialty.
Required outcomes: The draft can be copied or downloaded and has not been sent to the studio.
Currently in use: The current form selects positions from the same team source and creates a draft in the browser.

No personal application data is stored on the server or sent externally automatically.
This is not yet application intake or member onboarding.

QT0015Process version1.0.0

Team coordination · Not implemented

Online application intake

Receive and process applications through a real channel when an appropriate implementation request exists.

Lead CHRO

Scope and required outcomes

When to apply: The CEO authorizes implementation and decides the intake channel and data-handling responsibilities.
Required outcomes: Received applications have a real acknowledgment and a handler, within the agreed scope.
Currently in use: Actual submission remains deferred; only draft preparation is currently available.

No intake channel, application storage, receipt confirmation or automated recruitment process exists yet.

Technical

QT0006Process version1.1.0

Technical · Implemented within the stated scope

Look up work by ID

Validate the work ID, read through the data-access layer and return the portion allowed for public access.

Lead CTO

Scope and required outcomes

When to apply: Open a work record or call the read API with a specific ID.
Required outcomes: A valid work item, or an error that distinguishes an invalid ID from a missing record.
Currently in use: Server-rendered pages and ID-based reads get work from the studio API when the server is configured; otherwise they use local data. HTTP 400/404 distinguish invalid IDs from not found.

This process has no write operation.
Local data is read only when no source is configured; this path will be removed after work fully moves to the database. If the source fails to respond, the page reports an error rather than switching to local data.
Legacy work URLs still redirect using the mapping in code.

QT0007Process version1.1.0

Technical · Implemented within the stated scope

Read paginated work lists

Read part of the list with filters and a continuation cursor, enforcing the per-page limit.

Lead CTO

Scope and required outcomes

When to apply: View the work list or load the next results page.
Required outcomes: A page of public data, with a continuation cursor when more results exist.
Currently in use: The repository validates queries, project filters and the 1–50 items per-page limit; when configured, the server reads the list from the studio API and paginates in the database; otherwise it uses local data.

Local data is read only when no source is configured; this path will be removed after work fully moves to the database. If the source fails to respond, list pages report an error rather than switching to local data.

QT0008Process version3.1.0

Technical · Implemented within the stated scope

Record contributions in the work log

Record significant contributions against COO criteria under the correct member ID; retain history and receipts, without separate events for minor work or isolated decoration.

Lead CTO

Scope and required outcomes

When to apply: A round of advice, execution or review has a real result worth recording.
Required outcomes: A new event is saved with a receipt, or a clear error enables the writer to handle the correct status.
Currently in use: Since 02/10/2026 the log has been in the studio API: the tool submits an event with the expected revision; the server validates data, revision, duplicate event IDs and credential permissions, writes an audit record and returns a receipt. The local file is only a backup.

Only authorized writers use the internal API; no public write route exists. Agent-written events have internal visibility.
Internal event bodies cannot yet be read back; handover relies on the receipt and states what was not reread.
When delivery is uncertain after a connection loss or backup-file cleanup error, check the exact submitted event ID; do not create a new ID to write it again.

QT0009Process version1.1.0

Technical · Implemented within the stated scope

Read a member profile

Combine identity, assignments and workspace by member ID, exposing only public data in the interface.

Lead CTO

Scope and required outcomes

When to apply: Open a member’s page or request their profile through the repository.
Required outcomes: The correct person’s profile, not found, or a clear source-read error; internal evidence is excluded from the interface.
Currently in use: Member pages render on the server through the same repository. Since 02/10/2026 current work, upcoming work, weekly plans and public history read from the studio API; identity, roles and assignments still come from source code. The local file is only a backup for runs without the API.

A public profile is not an account or access permission.
Identity, roles and assignments are still edited in source code; this part has no administration API yet.
If the API fails to respond, profiles report an error instead of using the backup; the backup lacks data written after the 02/10/2026 source cutover.

QT0010Process version1.0.0

Technical · Implemented within the stated scope

Read paginated contribution history

Filter public events by member and retain continuation position as new events arrive.

Lead CTO

Scope and required outcomes

When to apply: Read a member’s history or move to its next page.
Required outcomes: Events for the correct member, in order and within the limit, with a continuation cursor if more remain.
Currently in use: The cursor binds to a member and a public event; the default is 10, with at most 50 events per page.

An invalid cursor cannot return internal evidence or another member’s events.

QT0011Process version1.0.0

Technical · Implemented within the stated scope

Synchronize AI role configuration

Generate tool configurations from shared profiles and check consistency.

Lead CTO

Scope and required outcomes

When to apply: Add a role or change a profile, shared instructions or rules version.
Required outcomes: Configurations generated from one source, or explicit conflicts and unsynchronized parts.
Currently in use: A generation/check tool validates names, duplicates and files outside its management authority.

Matching configuration files do not prove a tool loaded them or ran an agent.
No accounts, permissions or automatic schedules are created.

QT0012Process version1.0.0

Technical · Implemented within the stated scope

Synchronize the rules-set version

Synchronize version marks from one source and check files belonging to the same set.

Lead CTO

Scope and required outcomes

When to apply: A rules-set change has an agreed, appropriate version increase.
Required outcomes: Version marks match the source; the responsible person still checks policy content.
Currently in use: A tool synchronizes and checks versions, using the same source for display.

A synchronized version number does not prove agent compliance or execution of a process.
The rules-set version differs from individual process versions and data revisions.

QT0013Process version1.0.0

Technical · Not implemented

Grant, change and revoke system permissions

Link profiles to accounts, enforce approved permissions and check access results.

Lead CTO

Scope and required outcomes

When to apply: Approved permission needs exist and the account system is ready to implement them.
Required outcomes: Permissions granted, changed or revoked for the right person and environment, with evidence of checks.
Currently in use: Only lifecycle responsibility guidance exists so far; the website has no account, login or permission-management system yet.

Automatic account creation, session disabling and permission revocation are not yet available.
HR Admin is not automatically a system administrator; the operator must be authorized.

QT0016Process version1.0.0

Technical · Guidance available

Verify and hand over website changes

Choose checks suited to the change, apply relevant review and reconcile results before handover.

Lead CTO

Scope and required outcomes

When to apply: A code, data, content or interface change needs acceptance within its assigned scope.
Required outcomes: Checks match the scope, limits are explicit, and failures are resolved or handed over for continuation.
Currently in use: Guidance, check/build commands and tests exist; screenshots, browser interactions and review must still be performed for each relevant task.

Do not deploy or publish the website autonomously.
A passing build does not replace display checks; simulated tests do not prove behavior on every real device.