Apply this competence to the work described below. The public edition 0.3.2 includes its method, operating knowledge and worked examples. Add your context after the supplied knowledge. Use execution tools only if this host provides them.

# Compose Agreement Contract

Form an agreement's architecture from parties, intended result, exchanges and dependencies. Make scope, contributions, rights, obligations and unresolved choices explicit before drafting.

Use this competence when a collaboration or service needs a clear agreement and standard clauses do not describe the work. Relations clear in separate conversations may conflict when combined. Form an inspectable, revisable architecture. Document precision comes from the actual relation; legal sufficiency requires the sources and qualified competences pertinent to the case.

## Understand what should become possible

Begin with the intended result and relationship sources: participating people or organizations, actual roles, object and discussion state. Do not immediately fit the case into a standard contract. A map of issues to agree may be the useful first result. Preserve the person's words and choices while keeping unresolved matters visible.

## Connect contributions and dependencies

Make understandable who offers what, to whom, when and under which conditions. Connect performance, resources, payments, access and acceptance evidence where relevant. A delivery may depend on materials another party must provide; payment may reference an event nobody has defined. Bring these relations into one field before drafting apparently precise commitments.

## Compose the necessary knowledge

Project knowledge clarifies feasibility and deliverables; economic knowledge clarifies exchanges and negotiating position; writing gives definitions and consequences precision. None should invent the truth owned by another. For use as a legal instrument, reach current primary sources for the jurisdiction and the qualified legal competence needed. If unavailable, prepare structure and precise review questions without claiming legal sufficiency.

## Form a coherent whole

Consider rights, obligations, conditions, duration, changes, exit and continuing relations where they affect the agreement. Ownership, reuse, data and confidentiality may matter in one case and be absent in another. Do not fill unknowns with conventional wording. Understand how definitions interact: a responsibility, deadline or acceptance criterion can change other sections' meaning.

## Choose the form serving discussion

The result may be a relationship map, term structure, draft or comparison with a received document. Write so parties can see what is aligned and what needs a choice. A counterpart's response can change the next agreement without rewriting the provenance of earlier requests. Distinguish proposal, revision, acceptance, signature and performance.

## Preserve authority and learning

Composing and writing do not send, accept, sign, pay, transfer rights or grant access. Keep each effect connected to the relevant person, means and authorization. After a real case, retain what changes later composition: hidden dependencies, ambiguous definitions, missing evidence or confused roles. Return legal learning to qualified sources and project or writing learning to their own methods.

## Method depth

The object is an agreement's architecture. This is a domain competence that can compose other knowledge; composition alone does not make it a competence generator or autological faculty.

It can learn about its own method when a case reveals an ignored dependency, such as delivery depending on client data that the structure failed to expose. Correcting composition helps later agreements without providing a legal guarantee or authority to bind parties.

## Learning and continuation

A concrete case can change recognition of dependencies and responsibilities. Retain the correction's reasons and let each new context determine pertinent relations rather than making every clause universal.

Begin from available context and sources. The method can operate in chat; persistence, tools and external actions follow the recipient's means and mandate. Observe behavior and value in real work.
## Reachable operating knowledge

Read [OPERATING_GUIDE.md](OPERATING_GUIDE.md) as part of this method when forming the work. It carries the practical knowledge, decision relations and available means for this capability. The complete chat starter includes this knowledge and worked examples, so it remains usable without private sources. Preserve the public source identity and adapt through the recipient's actual means.

# Compose Agreement Contract

## Form the agreement's operative architecture

Understand the actual parties, purpose, contributions, deliverables, acceptance, resources, rights and dependencies before selecting a contract form. Connect money, milestones and responsibilities to what each party can supply and decide. For an AI or research arrangement, distinguish source knowledge, existing intellectual property, generated work, licenses, data access, confidentiality, maintenance and authority over external actions when those relations matter. Do not turn every project into the same contractual template.

Expose a missing domain owner rather than asking business prose to invent the underlying relation. A technical source establishes what the product actually does; the business owner supplies selected commercial direction; qualified current legal sources and professionals supply legal interpretation where needed. The competence forms the operative arrangement without claiming enforceability from a coherent draft.

Write the selected document in clear terms that preserve those dependencies. A late change to rights or acceptance can affect payment, delivery and termination; follow the actual dependent clauses without rewriting unaffected terms. Keep negotiated determinations, unresolved points and assistant alternatives distinct. A term sheet, draft, agreed text, signature, filing and performance are different effects. Preserve version and exact selected parties/document before any authorized send or signature action.

# Compose Agreement Contract — application examples

[Italiano](ESEMPI_IT.md). The following cases illustrate how the method is used.

## Make a research collaboration’s commitments explicit

Two groups share materials and intended results. Make contributions, access, timing and reuse questions visible for agreement. Do not invent ownership or a licence when the parties have not determined them.

## Connect a service delivery to client-supplied data

Delivery depends on data the client must provide. Connect data availability, the supplier’s work and acceptance criteria in the agreement architecture. Open choices become precise questions for the parties and relevant review.

## Find inconsistent definitions in a received draft

A draft discusses completed delivery and payment but uses different definitions of the same result. Identify the mismatch and its operating consequence without automatically substituting clauses or declaring legal validity.

## Apply the method to your case

Use [SKILL.md](SKILL.md) or [START_CHAT_EN.txt](START_CHAT_EN.txt) with the relevant sources and your actual context. Keep observations, interpretations and what remains open distinguishable. Preserve the useful reason and continuation in the project’s guide.


# Your context

Intention, sources, existing work, available means and entrusted actions: [add here].
