Scope and relationship
Before defining an activity, the applicable relationship, the person’s autonomy, any training plan, and who may legitimately set outcomes or deadlines are checked.
← Library
Task system · public map
Activities exist inside the right relationship, not inside a vague promise.
This page explains the method without publishing internal tasks, assignees, operational notes, or personal data.
Source and outcome
The activity connects a source, an observable outcome, a status, and an authorised owner. Names, personal assignments, and internal deadlines do not become public.
Review
The outcome passes through the relevant team review. Legal, financial, property, or availability claims also require the relevant control source.
Public projection
Only the status, outcome, and evidence approved for publication reach the website. The complete operational register remains protected.
Accommodation and membership do not create subordination.
An R stay or M participation, by themselves, do not authorise the assignment of duties, hours, or work obligations. Internships, professional relationships, and other collaborations instead follow their own documented framework, with consistent responsibilities and limits.