MAIOS / AI activities to adapt
Understand what changed, compare it with what readers encounter, and carry useful corrections into public pages, guides and downloadable resources.
A project can develop new capabilities while its website continues to explain an earlier form. This activity reconnects current knowledge with public communication. It can correct an explanation, improve a guide, form a reusable resource or preserve a presentation that still serves its readers. Its method develops through the work it performs.
First public edition · 0.1.0
Begin with the project's purpose, current work and intended readers. Understand what those readers need to recognise, decide or do. A new name or release is one possible signal; a change in meaning, capability, ownership, maturity or practical use can matter without a new folder or version. Let the sources and the work change your question when they expose a relation the first description missed.
Read the relevant product or domain sources, their operating guides and the public surfaces that depend on them. Include contributions already published by other people and work that remains proposed or under review. Preserve the author of a statement, when it was supported and the scope of any observed result. A previous activity report locates knowledge; it does not replace the current owning source. If useful knowledge already exists but the activity cannot reach it, repair that connection rather than inventing a second method.
Follow the reader from a resource card or search result to the explanation, first-use instructions and material delivered. Ask whether that path makes the object, context, capabilities and conditions of use understandable. Compare the operating knowledge as well as the visible page: a correct title can accompany an incomplete method, and an updated page can still deliver an earlier archive. A linked assistant or another knowledge consumer may receive its own copy, index or source access; inspect its actual contract before deciding that it has changed.
Keep presentations that remain faithful and useful. When a difference matters, correct the responsible explanation, method, example, entry point or delivery mechanism. A reusable capability may merit a complete new resource; it may also be better served by an existing resource. Explain what another project must supply and what can be adapted. Preserve the reasons and practical knowledge that make the capability work, including relevant tools and recovery behaviour. A list of competence names or the removal of private paths does not convey that knowledge.
Give the title a recognisable object and context. Explain a concrete task, why the method helps and how to begin. Use examples from appropriate domains and mark invented cases as illustrative. Distinguish an available method, an implemented capability, an observed execution and a result that remains possible. Preserve maturity supplied by the source; a file edition does not establish general reliability. Structure the reading so that explanation, sources, examples and action can be found without reconstructing the project's private history.
Use the current contracts and tools of the website, repository and other owners involved. Follow the dependencies changed by this work: language counterparts, guides, starters, packages, catalogue entries, inbound links and discovery data. Update a separate assistant snapshot or runtime only through its own available means and the authority entrusted for that exact effect. A website publication can be complete while a separately owned runtime has a precise pending continuation. Keep that distinction visible where it changes use.
Before writing, identify the actual working revision, target and contributions already present. Use an isolated branch or another owner-supported method when needed. Refresh shared state before commit, push or publication and reconcile relevant changes without absorbing unrelated work. Perform the effects the person has entrusted, such as preparing changes, publishing selected pages or releasing a resource. If one action needs a decision or unavailable access, prepare its concrete continuation and keep independent work moving. Verify the exact delivered result: the committed files, downloadable package and live route have distinct identities.
A missing source, repeated finding, misunderstood explanation or successful new approach can change how the next movement should work. Return the reusable difference to the competence, guide or entry point responsible. Improve your own instructions within the delegated range. Before changing a native scheduled job, read its current identity and configuration, preserve a complete private before-state, apply the authorised change, read back the saved result and preserve the complete after-state. Keep secrets out of exported backups. Purpose, cadence, recipient, spending and authority over publication remain the person's determinations unless their change has also been entrusted.
Maintain a short current note that reaches the reasons, sources, changes, effects and genuine pending actions in the project's working guide. Preserve a deferred possibility with the condition that would reopen it. A quiet run can be useful; do not manufacture edits, alerts or new resources. When nothing actionable has changed, follow the recipient's notification preference. Report meaningful consequences, a new impediment or a concrete decision needed, distinguishing preparation, publication, observed use and later learning.
Illustrative case. A planning tool gains an offline workflow, but its public guide still assumes a permanent connection. The activity reads the owning implementation and release notes, distinguishes the released workflow from an unfinished synchronisation proposal, and follows the user path through the feature page, guide and example file. It updates the entrusted documentation in both languages and checks that the example delivered is the current one. Learning: later comparisons must follow the workflow's conditions of use, even when the feature name stays unchanged.
Illustrative case. A museum has improved how facilitators adapt a workshop to different sensory needs. A celebratory page alone would not transfer that ability. The activity forms a usable guide with the decisions facilitators make, accessible materials, three situations and a first assignment. Participant records stay private. The owner still describes the method as developing; the public introduction preserves that state. Learning: future resources must carry the practical choice-making knowledge as well as an attractive description.
Illustrative case. A group publishes a revised model while a public explainer still presents an earlier hypothesis as settled. The activity reads the paper and the group's qualified account, then revises the affected explanation and teaching example. It preserves what remains unresolved and routes a separately owned teaching assistant's source update through its actual owner. Learning: updating the visible page alone does not change the material that another consumer receives. A quiet later run keeps the still-correct explanation.
Illustrative case. A community project repeatedly receives reports that its website is unchanged, although a source guide has acquired a better operating method. The activity recognises that it was comparing versions and page text while missing the practical knowledge in the guide. It changes its source entry and continuation instructions within the entrusted range. If this changes the scheduler's prompt, it preserves the complete private configuration before and after and reads back the real job. Learning: improve the point where knowledge failed to participate, rather than creating a second recurring audit.
Select an actual website or public resource and the project it represents. Supply the current sources and name the intended reader. You can begin with one product guide, a collection of educational materials, a service website or a research programme. The activity can work across several surfaces when the same entrusted purpose makes that useful.
Open START_CHAT_EN.txt and copy or attach the whole file to your AI. Add CONTEXT_EN.md or describe the same information in your own words. The starter contains this activity's complete method, practical guidance and examples. If the AI cannot read a source, supply an accessible copy or keep the missing relation explicit. Save the working guide returned by the conversation so a later session can continue from it.
Keep the complete activity folder in your project's working knowledge and make ACTIVITY.md the entry. The package includes the full public folders of three supporting competences under skills/: Form Public Meta-Skill Resources forms the transferable resource; Meta-Activity connects mandate and controller; Situated Activity Evolution improves the recurring work through consequences. If your environment uses discoverable skills, follow its native installation rules for those folders, preserving existing versions. An activity is an entrusted assignment that composes these capacities; its folder is not itself a scheduler.
For a first run, ask the AI to use the activity on the selected project now. To make it recur, select a suitable event or cadence, timezone, recipient and notification preference. Give the actual controller an entry that can reach the method, project context and current working guide. Use the controller's native creation and readback tools. Record the identity and full configuration privately. If the environment has no scheduler, the same method remains usable on request; a saved prompt does not configure a recurring job.
State which repositories and public surfaces the AI may change and whether it may publish directly. For example, you can entrust routine documentation corrections and resource updates while keeping pricing or scientific claims for a separate decision. Scope this to the actual project rather than inheriting the MAIOS activity's permissions. Provide tools and access through the receiving environment; put no credentials in a public context template. Once an effect has been entrusted, carry it through without asking again for each reversible mechanic.
Inspect a representative reader path and the material it delivers. For a changed package, compare the released bytes and its stated source; for a new explanation, check the generated language and first-use path. Appropriate checks follow the property at stake. Preserve what the observation actually establishes. A correct page or passing test does not establish another person's understanding, adoption or a model's assimilation. Continue from new consequences rather than repeating an unchanged verification.
Read the complete starter or add your context here. The text is prepared in your browser and stays on your device. Use it now and choose a recurrence when useful.
The kit includes these three complete public competences. The starter already supplies the method needed to begin in chat.
Adapted from the recurring activity used to maintain MAIOS public resources. The original activity has produced resource and website updates. This portable edition supplies its operating method and illustrative adaptations; use in another project has its own results to observe.
Activity source and Apache-2.0 licence ↗
AI activities to adapt ↗