What this wiki is for

This wiki should turn confirmed organization facts into a plain-language reference: who is active, what each named person owns, how work moves, and which boundaries protect owner approval and internal-only operations.

It is an information-architecture and content draft, not an authority to change organization data.

Source: orgdata/tasks.jsonl; orgdata/sops-nok.json

Problems to make visible

Incomplete organization facts

The canonical record leaves unresolved: complete headcount beyond confirmed records, reporting-hierarchy details, LINE room/bot mapping, and historical worker status.

Role and identity confusion risk

Every active agent needs a stable name and person_id. Anonymous, temporary, or capability-only workers cannot receive tasks.

Approval and boundary risk

Owner approval remains required for external hiring, payment, external accounts, credentials, production publishing, and external messages.

Delivery tracking is overdue

The implementation and content child task have overdue deadline/checkpoint watchdog blockers. This preview does not alter task tracking.

Sources: orgdata/organization.json; orgdata/blockers.jsonl; orgdata/tasks.jsonl

Core concepts

  • Confirmed active: named person with status confirmed_active.
  • Person identity: stable pair of display name and person_id.
  • Responsibility: work a person is recorded as owning or performing.
  • Boundary: explicit “do not” or scope limit.
  • Unknown: unconfirmed fact; it must not be inferred.
  • Evidence-backed claim: statement linked to a source path.
  • Approval status: draft/unapproved content is not permission to publish or communicate externally.

Confirmed organization structure

Coordination and project operations

Sol / โซล (sol)Coordinator — receives owner requests, coordinates with Mek, and reports verified results to the owner.
Boundary: single owner-facing voice.
Mek / เมฆ (mek)Project manager — prioritizes work, decomposes tasks, assigns workers, tracks deadlines, reports blockers, and summarizes results.
Boundary: owner-facing communication routes through Sol.

Named specialist roles

Win / วิน (win)Internal IT support.
Internal systems only; no unapproved production/account changes or external communication.
Nat / นัท (nat)Money — spending, bills, and financial organization.
Ing / อิง (ing)Health — sleep first, then skin and fitness.
Pim / พิม (pim)Relationships — calls, visits, and communication consistency.
May / เมย์ (may)Spam-monitoring worker — classifies incoming mail, handles confirmed spam within permission, and reports through May → Mek → Sol → owner.
Must not communicate with customers or mutate uncertain/allowlist mail.
Nok / นก (nok)Information architect and content editor — converts owner-approved facts into wiki structure and tracks citations, unknowns, and approval.
No invention, external communication, publication, or public URL.
Fah / ฟ้า (fah)Web design and documentation builder — implements approved content locally or in staging with responsive/accessibility/navigation requirements.
No production domain, hosting, publishing, public URL, or unapproved content/assets.

Explicitly unknown structure

  • Complete headcount beyond confirmed records.
  • Reporting hierarchy beyond the recorded Sol/Mek route.
  • LINE rooms, bots, and mappings.
  • Historical worker status.

Confirmed workflow

  1. Intake and coordination. Sol receives owner requests and coordinates with Mek; owner-facing reporting routes through Sol.
  2. Planning. Mek prioritizes and decomposes work, assigns named workers, tracks deadlines, reports blockers, and summarizes results.
  3. Worker execution. The worker reads the task/SOP, acknowledges, executes within scope, reports checkpoints, attaches evidence, and reports blockers immediately.
  4. Content-specific execution. Nok structures and drafts evidence-backed content, marks unknowns, and submits to Mek.
  5. Review gate. Mek reviews content, scope, and evidence; Fah depends on approved content.
  6. Safety boundary. No publication, public URL, external message, or prohibited external change is part of this task.

Citation and review ledger

SectionEvidence statusSource
Purpose and scopeConfirmedorgdata/tasks.jsonl; orgdata/sops-nok.json
Problems and unknownsConfirmed; unknowns retainedorgdata/organization.json; orgdata/blockers.jsonl
Named structureConfirmed active records onlyorgdata/organization.json
WorkflowConfirmed SOP/task workfloworgdata/sops-worker.json; orgdata/sops-nok.json; orgdata/tasks.jsonl
Approval/publication statusLocal-only preview; no external actionorgdata/tasks.jsonl; orgdata/sops-fah.json

Open questions for Mek/Sol review

  1. Confirm whether any additional active people should be added.
  2. Confirm whether a reporting hierarchy exists beyond the recorded Sol/Mek route.
  3. Supply or explicitly defer LINE room/bot mapping.
  4. Confirm treatment of historical worker records.
  5. Confirm whether Mek approves this content for the local-only preview.