
# Meta-Focus

Forms a shared orientation for complex work by connecting its purpose, responsible people, knowledge, means and next useful contribution.

An exhibition may already have objects, texts and technicians available while lacking the connection needed to decide what to do today. Meta-Focus makes that relationship readable where the work continues.

The method is still being formed. The public examples are illustrative; the file version identifies the edition and does not establish maturity across environments. The competence adapts to the guides and tools you already have.

## Prepare an exhibition while its contributions are still separate

The curator keeps the selection of objects; the technical team knows the room; an association is preparing captions. Another room has become available.

Today’s work needs to be situated again: who leads the decision, which sources and competences could change it, and which action is actually possible? The exhibition guide may already hold these connections.

## Adapt the focus to your project

Preserve the relationship between the selected work, those responsible for its decisions, knowledge that must participate, available means and consequences. Domain, people, sources, tools and memory location change. One person working with an assistant may need it as much as a group.

Bring still-valid work, a concrete situation and existing guides. Focus can emerge while you act: a simple request needs no new document, and an adequate guide should be reused.

## Recognise the object, purpose and still-valid decisions

Begin from what the person wants to achieve and the work that already exists. Understand which object can change and why it matters now. A recent file, tool name or word in a request does not identify its responsible owner by itself. Continue when the work is determined; reach a missing relationship when it could change the result, without reopening every decision.


## Enter through the place that owns the work

Reach the guide, present state and sources of whoever owns the work. Use that location if it already retains the necessary connections. If material complexity risks scattering them, form a small live margin there that makes current work, contributions, tools and continuation understandable. Documents and evidence remain with their owners; the margin connects them without becoming a second authoritative copy.


## Let the competence that changes the choice participate

Read the operating body and practical knowledge of pertinent competences while forming the question and action. Describe an actual contribution when continuation needs it; a nearby or still-to-be-acquired capability retains that state. A list of names does not prove consultation, installation or exercise. Domain method stays with its competent owner even when several specialisms contribute to one work.


## Connect actual tools and entrusted effects

Understand which sources and tools the receiver can reach and which actions it has been entrusted to perform. A readable guide does not grant control of the service it describes. Identify the missing condition for a concrete action and continue independent work. A shared file preserves information but does not automatically notify or wake another person or AI.


## Continue from changed understanding

A source, result or correction may change the question, relevant owner or useful means. Use what you have understood now, in the present from which you choose how to continue. Logical consequences remain possibilities: the chain of your first interpretation does not decide the next act by itself. Preserve a still-valid determination and reform focus where the new difference requires it.


## Preserve contributions proceeding in parallel

Before writing, reread the exact object and its current version. Change your own delta in the entrusted location; if another contribution has advanced, reread and compose it without blind replacement. Where the means offer revision protection, use the freshly read identity and read back the result. This protects that write without installing a distributed lock or automatically settling a disagreement about meaning.


## Continue results and learning in their respective homes

When a material difference changes the work, retain its source, acquired understanding, result, actual state and next movement or resumption condition. A method correction returns to the competence that must act differently; the margin keeps the connection. Prepared, written, received, exercised and assimilated are different facts. Stop when another passage changes no useful relationship, without producing updates to fill a quota.

## Continue through the actual project

Keep the relationship enabling the next choice in the work’s existing home, retaining sources and observed states.

Return reusable differences to the competence that must act differently. The edition makes the method available; its use and assimilation require their own observations.

## Operating knowledge

Read OPERATING_GUIDE.md and EXAMPLES.md. With no file access, use the complete START_CHAT_EN.txt. The method composes with complementary project competences; actual tools, persistence and authorized effects belong to the receiving environment.


# Meta-Focus — practical operating knowledge

## A short margin can reach deep knowledge

The margin supports resuming a choice: what is being done, why, who owns it, which contributions remain causal and which event could change it. A reference suffices only if the next receiver can reach it and recover its reason. When files are inaccessible, keep essential knowledge in the note or prompt that will actually be available. Do not copy the entire archive at every reentry.


## Operating focus, method and continuity make distinct contributions

Focus connects work to its capabilities in the present; method formation understands how to approach it; continuity retains knowledge and reasons for proceeding. These functions can cooperate in the existing guide. Focus does not become the supervisor of all competences or automatically assume another person’s or instance’s work.


## Availability does not establish use

An assistant may read a method without possessing the tool needed to carry it out. A capability may be installed but not invoked; a written contribution may not yet have reached its recipient. State the relationship that matters for the present act. A statement or footer can make participation readable, but does not produce it or authorize a mutation.


## Responsibilities can change with the question

In the exhibition, the curator retains the curatorial decision while the technical team qualifies the room’s availability. If a different question about the visitor’s experience emerges, the person competent to design it becomes pertinent. Focus keeps that passage reachable without transferring every project truth to one owner. A complete organizational chart need not be fixed in advance.


## Concurrency involves identity and meaning

A Git revision or service version check protects one exact body. It does not establish that two proposals are compatible, that another AI read the changed text, or that effects cannot be duplicated. Keep contributions and their observed states attributed; the integration owner composes meaning. A coordinator or automatic synchronization needs its own means and mandate.


## Use the state form the project already supplies

A chat may retain a note; a file-based project may use its CURRENT or guide; an agentic environment may have validated state transitions. Use the means that preserve the relationship and respect their contract. Do not write directly into validated state to bypass its transitions. The method transfers a connection rather than prescribing a file, schema or new runtime.


## One learning may have several destinations

One event may change domain knowledge, how a method is formed and the connection that previously left a competence unreachable. Keep the event at its source and return only the difference that changes each responsible owner’s work. If the knowledge already existed but did not participate, correct its entry; repeating the same note across every competence does not repair that failure.


## Connect the project to knowledge that could change its work

At project entry, reach pertinent competences and sources while observing and choosing the contribution. The project uses shared knowledge and returns reusable differences during the work to competences that must act differently. Knowledge can also change the object recognized and the question asked; placing it only as information inside a fixed frame can leave that frame’s limit intact. Exercise this relation through the existing guide without a second supervising boot or a reading of the whole system.

## Focus becomes more precise through work

This resource shares a method still being formed. Its first source exercises show situated connections between tasks and competences; they do not establish automatic activation, universal coordination or measured time reductions. These cases and the exploration are illustrative.

You can use it without adopting a new system: continue through the guides and competences you already have. A different use may show where the connection helps and where it should change.


# Worked examples

Illustrative cases. Conditions, decisions and continuation are supplied to teach the method; these are not reports of customer results.

## A new room recomposes the exhibition’s work

A museum is preparing a small exhibition. The curator has selected the objects, an association has draft captions and the technicians know only the old room. A different space becomes available. The AI reaches the exhibition guide and connects the new room to today’s question: preserve the route or change it? The curator owns the narrative decision; technicians qualify space and means; whoever designs the reading experience understands how visitors will encounter the objects. The first useful contribution is a reasoned arrangement proposal based on those sources. The guide retains what is proposed and what has been accepted, together with the next necessary conversation. No new organizational chart is created, and room availability is not approval of the installation. At reentry, the next AI reaches the reason for the arrangement as well as its final drawing.


## Two assistants change different contributions to one manual

A cooperative is updating a maintenance manual. One assistant prepares images; another revises explanations with the technicians. The manual’s guide identifies both contributions, their sources and the edition’s integration owner. Before writing an explanation, the second assistant rereads the current text and finds a correction just entered by a technician. It preserves that contribution, changes only its own passage and reads back the resulting version. The image assistant can continue independent work, but neither assumes it has already received the revised text. The integration owner connects the affected caption to the changed meaning. The case teaches the difference between a revision-protected write, integration of knowledge and actual reception; the method installs no distributed lock or messaging service.


## Resume an experiment when the available instrument changes

A research group retains a question and an experiment paused because of a measurement limit. After an interruption, a collaboration makes a different instrument available. The AI reads the working guide, the reason for pausing and actual access conditions. The researcher understands that a different question is now useful instead of merely repeating the old plan. Focus connects the new object to pertinent scientific knowledge, the instrument’s owner and necessary analysis. The guide retains the proposed experiment and what remains to be agreed. The continuity method learns which reason the former summary omitted; scientific knowledge stays in its domain. Announced access, a planned experiment and an observed measurement retain distinct states. Reentry uses acquired understanding in the present instead of turning a deduction from the old plan into an obligation.


## Shared knowledge changes both the project and its common method

A cooperative maintains equipment at several sites. A new assignment appears to ask for guide reorganization, but its entry reaches shared knowledge about responsibility and maintenance. Sources show that the same spare-part label refers to two different components: the useful question becomes which identification technicians need before intervention. The project keeps that technical distinction and involves its competent owner. The shared continuity method receives a smaller lesson: retain component identity with the reason for a reference where that difference changes the next action. The project guide reaches both contributions without copying them into every file. System and project support each other; writing the guide does not install its method at every site or in future assistants.


My assignment, sources, existing work, available means and requested result:
