Released v2.4.0
Build source-backed personal work memory, a fixed-time Email EA and a reconciled Drive master index, with visible controls and proof.
These are separate, verified public downloads. Configured v2.0.0 through v2.3.0 workers can take v2.4.0 at a safe checkpoint with user-owned state preserved. Pre-v2 workers first use the guided exact-scope Gate 0 migration.
Two clean downloads
The editions are deliberately separate. Do not give the Kairali package to an outside user and do not give a Kairali employee the generic package.
Includes the Kairali Setup Helper, role prompts, Personal Work Memory + Daily Email EA, Drive Master Index, the human-only Saturday LinkedIn assistant and reference skill packages. v2.4 never activates a skill.
Download Kairali employee editionContains only the company-neutral workspace, generic Setup Helper and reversible lifecycle controls. It is tested to contain no Kairali employee content.
Download reusable editionInstall in five steps
No Terminal, PowerShell, Python, Git or typed command. The Setup Helper performs the internal work and gives you only an unavoidable click, login or permission.
Click the Kairali employee download or reusable download above.
DONE WHEN: the ZIP is in Downloads.Mac: double-click the ZIP once. Windows: right-click it, select Extract All, then select Extract.
DONE WHEN: the named edition folder appears.Use the desktop app, sign in with the correct account and start a new chat.
DONE WHEN: the new chat box is visible.It asks one question at a time for the exact company/entity, unit, jurisdictions, purpose, your relationship and compliance owner. It checks current sources before creating the working copy.
DONE WHEN: Codex shows the correct local project and confirmed Gate 0 profile.Paste the startup test from START-HERE.md. Change nothing until the identity, scope, Gate 0 and state readback is complete.
DONE WHEN: the exact profile, ACTIVE and validator PASS are visible.Fast for ordinary work
v2.4.0 adds an evidence-bound monthly or quarterly improvement loop with approved official, Reddit and YouTube research. It turns repeated work into proposals for your judgment while every external effect remains off.
A question or source review gets an answer without creating task state, facts, decisions or tool rows.
PROOF: useful answer, no workspace diff.A clear local file request uses standing worker-local permission. The lifecycle runs behind the scenes, reads back the artifact and keeps one usable undo.
PROOF: artifact readback and validator PASS.The worker reads the exact company gate, omits only the unsupported or unapproved part, finishes the safe local work and names the evidence or approval that would unblock the rest.
PROOF: safe result exists; gated effect did not occur.One document with 150 rows uploads intact as one artifact. Creating 150 GitHub issues is 150 external writes, so execution runs in batches of no more than 25 with a checkpoint between batches.
PROOF: no truncated file and no hidden bulk execution.Optional personal improvement
Choose monthly or quarterly. The worker can inspect only the local records, exact questions, official domains and research channels you approve. Every recommendation waits for your judgment.
Open the installed worker and say SET UP MY PERSONAL IMPROVEMENT REVIEW.
Select cadence, local time, time zone, local evidence, exact research questions, official domains and any approved Reddit or YouTube channel.
DONE WHEN: the complete preview is visible.Approve the preview, then verify the Scheduled card, cadence, exact prompt fingerprint and next run.
DONE WHEN: the worker says VERIFIED_ACTIVE, or truthfully UNAVAILABLE.Choose PROPOSE, dated LATER or REJECT. A proposal remains inactive until its separate proof path passes.
DONE WHEN: the choice appears in decision history.Supply minutes before, minutes after, observed occurrences and evidence. The brief calculates the time difference.
DONE WHEN: measured minutes are visible; money saved is not invented.Hard boundary: this loop cannot send email, unsubscribe, change filters, act on LinkedIn or install a skill. Those effects are unavailable in v2.4 because no trusted credential or skill-loader authority is shipped.
Gate 0 belongs to the exact company scope
The shared system defines how gates are researched, confirmed, stored and enforced. The actual gates come from one private profile for the exact legal entity and work being set up.
Company or group, exact legal entity, operating unit, jurisdictions, bounded purpose and your relationship to the company.
Use current official or controlled authoritative sources. Historical charts and remembered rules are only unverified leads.
Every gate names an ID, trigger, required action, source, approval owner and evidence needed.
The named compliance owner reviews the proposed profile. Unanswered compliance questions block ACTIVE.
Different companies, or materially different entities, units, jurisdictions or purposes, use separate worker folders and profiles.
The validator catches identity mismatch, overdue review, profile tampering and edited gate/source views.
Important: historical operations charts can help discover questions. They are not proof of current legal, certification, registration, tax, clinical or other compliance status.
One kind of data, one file of record
The installed workspace includes a complete WORKSPACE-MAP.md. This is the short version.
| What | File of record | What it stores |
|---|---|---|
| Identity and scope | COMPANY.mdPARAMETERS.mdROLE.md | Exact company/entity/unit/jurisdictions, user relationship, purpose, responsibilities and exclusions. |
| Storage map | WORKSPACE-MAP.md | The authoritative map that names which file owns each durable kind of information. |
| Active Gate 0 and work locks | .ai-human/control/gate-profile.jsonGATES.mdWORK-GATES.mdCOMPLIANCE-SOURCES.md | The machine profile, its generated human-readable gates and sources, plus separate task-specific operating locks that may narrow but never replace Gate 0. |
| Truth and rulings | FACTS.mdDECISIONS.md | Verified operational facts versus owner/compliance-owner decisions and supersession. |
| Tools and unattended work | TOOLBOX.mdAUTOMATIONS.md | Allowed tools/permissions and separately approved automations. Never credentials. |
| Current and queued work | MASTER_CURSOR.mdOPEN_REGISTER.mdTODAY.md | The one live task, the backlog and today's bounded working set. |
| Completion proof | COMPLETED_LEDGER.mdEVIDENCE_LOG.md | The completion index plus detailed checks, result, artifact/readback and undo evidence. |
| Shared system | .ai-human/system/AGENTS.md and adapters | Managed shared rules and local onboarding adapters, not company facts, user state or secrets. |
You stay in control
The local system and external account access are separate. Choose the smallest action that matches what you want.
If a request crosses a declared boundary, the AI names it briefly, refuses only the conflicting part, preserves safe work and offers the nearest compliant next step or exact approval needed. It does not scold, lecture or turn one guardrail into a broad ban.
First pauses and verifies any visible personal-improvement schedule, then turns managed rules and automatic updates off. Project files and account connections stay.
Pause any visible improvement schedule, then suspend this AI-human system and verify SUSPENDED with PASS.DONE WHEN: schedule cannot run, rules OFF, updates DISABLED.Turns the system back on and restores the automatic-update setting that existed before suspension.
Resume this AI-human system, then verify ACTIVE with PASS.DONE WHEN: rules ON, validator PASS.First removes and verifies any visible improvement schedule, then archives .ai-human and its active local adapters. It preserves work files and does not delete the project.
Remove any visible improvement schedule, then reversibly uninstall and verify UNINSTALLED with PASS.DONE WHEN: schedule, system and adapters are absent.Open Plugins, use Installed, open the plugin and choose Uninstall plugin. Disconnect its connector separately. Review Computer Use permissions too.
Official plugin instructionsDONE WHEN: a new chat cannot use that access.Important: suspend or uninstall does not disconnect Gmail, Drive, GitHub or computer permissions. Plugin uninstall can also leave its connector connected until that connection is managed separately.
Troubleshooting
At the first failure, paste the complete Setup Helper message from your edition and add the exact visible error. It gives one action at a time and verifies the result.
On Windows, select Extract All instead of opening files inside the compressed folder. On Mac, double-click the ZIP once. If that fails, keep it, download once more and let the helper compare the visible filename and checksum.
Make the extracted working folder the local project, not the ZIP or untouched source folder.
Stop. The package is not released and must not be installed for real work.
Start a new chat in the same project and verify SUSPENDED. A stale chat is not proof.
Verify UNINSTALLED. Any active AI-human adapter means removal failed and must be recovered from the receipt.
Disconnect the connector separately. Plugin removal alone is not account-access revocation.
Kairali employee edition only
Use the Setup Helper. The portal makes the approved starters available. It does not connect your accounts, choose your times or activate a worker. Each employee completes this readback in three separate local projects.
At one fixed local time, the EA shows a neat brief with priorities, follow-ups, useful reading, newsletter and filter proposals, and local replies marked NOT SENT. Memory is sourced, dated, inspectable, correctable, excludable and forgettable. Mark LIVE FOR ME only after the pilot, memory controls, automation and validator agree.
DRIVE-INDEX.jsonl is the AI file of record. One approved Google Sheet or otherwise DRIVE-REGISTER.csv is generated from it. Mark LIVE FOR ME only after both reopen under one generation with reconciled counts, every supported scope ends, and the weekly refresh is verified or declined. TEST 25 proves setup only.
If chosen, prove the schedule, right-level local control, YOUR TURN ON LINKEDIN handoff, manually supplied pilot and local queue. Reusable learning is saved only after explicit confirmation and can be corrected or forgotten. Otherwise record NOT ENABLED BY CHOICE.
Downloaded, installed or connected alone does not mean live. Show the local report, cursor, evidence and validator.
Managed updates
The release notice names the version and affected files. Open the existing worker and ask the Setup Helper to check. The check is read-only; applying waits for your approval at a safe checkpoint.
Kairali users paste CHECK FOR KAIRALI UPDATE. Reusable users paste CHECK FOR AI-HUMAN UPDATE. You never type a command.
The helper shows installed and latest versions, changes, live-task status, managed files and preserved employee state. No file changes yet.
A live task defers the update. Otherwise, say UPDATE NOW. The helper backs up, verifies hashes, applies only managed files and validates.
A configured v2.0.0 through v2.3.0 worker moves to v2.4.0 with user-owned state preserved. A pre-v2 worker completes the guided Gate 0 migration first. Keep the version, validation receipt and preserved-state proof.
Automatic: the stable portal follows the approved release and a session may check for a newer version.
Manual: the user approves the apply. GitHub Desktop Fetch/Pull synchronizes only the selected repository; it does not install this managed update.
Right-level access
The portal cannot grant computer access. The real permission prompt appears inside ChatGPT when the employee starts an approved Computer or Chrome task.
Close LinkedIn. Start the local request with @Computer. Approve only the visible local project and current task. Keep Ask for approval. Never choose Full access or Always allow.
Computer and Chrome control stop first. Codex shows YOUR TURN ON LINKEDIN and makes no screen, mouse, keyboard or browser action while LinkedIn is visible.
You copy no more than 25 conversations, close LinkedIn, return to the local project and say BATCH READY. You also review, paste and send every approved reply yourself.
Choose exactly one edition ZIP first. The remaining presentation, homework and facilitator files below belong to the Kairali training path.
Do not mix them. Kairali staff use the employee edition. Everyone else uses the company-neutral reusable edition.
Start here if you are setting up your own AI-human worker; company employees and external users follow the same identity-and-Gate-0 check.
Check first, approve at a safe checkpoint, then keep the receipt.
Personal Work Memory + Daily Email EA and Full Drive Index are required. TEST 25 proves Drive setup only. Saturday LinkedIn is optional after both pass.
Use these only when an approved amendment must be made and revalidated.
Use these in the room. The beginner deck stays command-free.
For technical volunteers after the beginner rollout ends.
Technical and owner path
v2.4.0 is the approved public release. Its exact source, checksums and release evidence are published together. Fetch/Pull updates a repository checkout, not an installed worker; configured v2.0.0 through v2.3.0 workers use the checked update path and pre-v2 workers use the guided migration. Interrupted managed updates stop ordinary work until the checked recovery path completes.
Update the governed source and regenerate affected presentation or homework files.
Automated gates check the workspace, downloads, canonical indexing controls and production build.
Vercel updates this stable portal after the reviewed GitHub change reaches the production branch.
The company sends the exact check prompt to no more than 25 employees. Setup Helper receipts and Monitor readback prove completion.