MALPv0.1.3

A platform team uses MALP to drop a `.malp/` into an unfamiliar service inside a large monorepo, capturing open questions, tribal knowledge, and a short SUMMARY so new hires can orient themselves. Each new engineer reads the existing malp before committing changes, preventing repeated archaeology. The FOB file tracks wherever the current debugging focus has narrowed.

A digital agency sends MALPs into each client project path at kickoff and refresh points, keeping concise summaries and detailed working notes outside the client's own repos. When a new account manager picks up the project, they open the malp to instantly understand status, unresolved decisions, and the current forward operating base. Attic stores retired client malps without polluting active context.

A computational research group places `.malp/` directories alongside experiment code branches to record hypotheses, unresolved findings, and next steps without adopting a heavy project management tool. The SUMMARY answers 'what is this experiment?' at a glance while NOTES holds the messy results and open questions. When an experiment is deprecated, the malp moves to the attic index so it stays discoverable but out of the way.

An indie developer runs MALP across dozens of personal side projects, using `~/.malp-home/MAP.txt` to list active paths and the attic for dormant work. Before diving back into a neglected repo after months away, they open the malp to recover context in seconds. The FOB captures the narrow task they were on when they last stopped.

Teams running multiple AI coding agents use MALP as a shared context protocol so each agent knows what has been probed, what remains unknown, and which path is the active worksite. The skill enforces that agents only read the malp the user requested and ask before cross-loading another, keeping token budgets and context windows disciplined. Attic and unindexed states prevent stale directories from silently polluting agent context.

The core MALP skill and file conventions ship as free open-source tooling, while a hosted service syncs `~/.malp-home/MAP.txt` across a team's machines and devices. Teams get shared discovery of active and attic malps without manually merging index files. The hosted tier also offers search across all malps in an organization.

Large engineering organizations license MALP as a governed context layer that enforces which paths agents may probe, tracks active vs attic vs unindexed state, and prevents unauthorized `.malp/` creation. Compliance and security teams get visibility into what context agents are reading. This targets regulated industries where silent cross-repo context loading is a risk.

A packaged offering bundles the MALP skill with templates, onboarding checklists, and handoff rituals designed for client-facing work. Agencies adopt it to standardize project reconnaissance and reduce ramp-up time when staff rotate between accounts. Add-ons include attic migration scripts and reporting dashboards summarizing project health.