mirror of
https://github.com/apache/maka.git
synced 2026-10-28 17:04:39 +08:00
Dante.Cloud
da614305c9
* feat(runtime-host): preserve active turns during Goal event waits Keep explicit WaitForEvent calls in their original Run and tool operation, with normal durable results, steering and precise cancellation. Support AI SDK direct tools and Code Mode, plus natural Goal waiting through the existing continuation and admission boundaries. Remove the PR3 yield bridge, gates, provenance and cancellation protocol without compatibility fallback. Retain neutral observations used by Assistant Matter, durable consumption and existing Runtime recovery. Limit source integration to the existing ShellRun source. Exclude GitHub CI, PR/review, file readiness, computer observation and the ACP Host tool bridge; preserve main's native computer waits and ACP executor behavior. Document the removed integrations and their independent scope rationale. Generated-by: OpenAI Codex * fix(runtime-host): retire persisted Goal wait cancellation grants Release the retired Goal wait grant while preserving credential identity, unrelated grants, and separately granted Session wait authority. Cover pending, active, and revoked credentials across rewrite and reopen. Generated-by: OpenAI Codex * test(runtime-host): await durable Goal authority in fixtures Wait through the public Goal query after observing the expected in-memory state, so persistence assertions cannot race authority commits. Hold the achieved commit in a regression case while preserving the original SQLite and clear/drain scenarios. Generated-by: OpenAI Codex * fix(goal): retire legacy event waits during upgrade Pause PR3/PR4 waits without replaying their continuations, and settle any outstanding source-Turn accounting once. Preserve historical admission and Runtime event provenance while rejecting new legacy admissions. Generated-by: OpenAI Codex
Maka documentation
This page is the authority map for Maka documentation. Code and contract tests remain the final authority when documentation disagrees with the implementation.
Where information belongs
- Root and package READMEs describe stable product entry points, public seams, and local ownership.
docs/contains current cross-cutting architecture, security, product, and validation contracts.docs/blogs/contains long-form explanations of Maka's design ideas; code and current contracts remain authoritative.- GitHub issues and pull requests contain implementation plans, migration progress, and time-sensitive TODOs.
docs/archive/preserves completed plans and superseded material for historical context. Archived documents are not current implementation guidance.
Start here
- Backend architecture (中文)
- Desktop architecture
- Renderer architecture
- Evaluation kernel
- Runtime package
- Computer Use package
- UI package architecture
- Security policy
- Collect evidence for a Desktop conversation problem (中文)
Blogs
- Log Is the Runtime: How Maka Uses an Append-Only Log to Manage Agent State and Context (中文)
- From Copy-on-Write to Mailboxes: Two Paths for Multi-Agent Scheduling (中文)
- From Stateless Functions to Agent Runtimes: The Serverless Scheduling Unit Is Growing (中文)
Current contracts
Runtime and Eval
- Goal event wait consumers (中文)
- SessionTodo lifecycle
- Desktop message queue
- Work Board contract
- Work Board Phase 1 surface
- WorkHub domain language
- WorkHub Coordination Session ADR
- Runtime resume architecture (中文)
- Runtime PDF rejection recovery
- Runtime Host architecture (中文)
- Peer Mesh architecture (中文)
- Remote Runtime Host setup (中文)
- Runtime resume extraction ledger
- Runtime resume Phase 3–4 implementation route
- Skill catalog policy
- Provider-hosted web search capability
- Agent Swarm
- Side Conversation
- Agent Graph stream scheduling (中文)
- IM 扫码接入 runtime architecture
- Backend architecture chapters
Computer use
- Foundation contract
- Model-loop foundation
- Evidence classes
- Provider evidence contract
- Host events contract
Frontend and validation
Release operations
Security and privacy
Historical material
- Runtime kernel extraction
- Runtime v2 architecture evolution
- Runtime v2 implementation notes
- DeepSeek Reasonix cost runtime design
- Documentation archive
Maintenance
- Add stable cross-cutting documentation to the closest section above.
- Put local architecture beside the code and link it from Start here.
- Keep progress and TODOs in issues or pull requests instead of copying them into stable documents.
- Move completed plans to
docs/archive/; remove a document only after its unique references are updated or no longer needed. - Prefer updating an existing authority over adding a parallel document.
- Keep PR follow-up records, incident investigations, and run logs in the pull request or
docs/archive/, not as new current contracts.notes/anddocs/local/are workspace-local scratch and stay untracked. - Do not commit PR or issue screenshots under
docs/. Attach temporary visual evidence on the GitHub thread; product hero/marketing images live under.github/assets/.