---
name: montelibero-mtla-info
description: Use this skill when answering questions about the Montelibero Association (MTLA), its landing website, public identity, participation model, principles, governance documents, communications, and safe interpretation boundaries. Do not use it for the entire Montelibero movement, TFM, MTL Fund (PFM), or other Montelibero-related projects except to distinguish them from MTLA.
---

# Montelibero Association — AI Agent Instructions

## When to use this skill

Use this skill for questions about:
- the `mtla.me` landing website and the public pages it serves;
- MTLA identity and public description;
- fixed participation and extraterritorial contractual jurisdiction;
- the Association Agreement;
- principles and public normative materials;
- MTL Court as referenced by MTLA materials;
- participation procedure and participation-status materials;
- Council, Assembly, MCC, Working Groups and other governance documents, only as documented.

Do not use this skill:
- for the Montelibero movement as a whole, except to distinguish it from MTLA;
- for TFM, Third Fund of Montelibero, or other fund structures;
- for MTL Fund (PFM), MTL Wallet, EURMTL, MTL City, or unrelated Montelibero projects;
- for legal, tax, financial, migration, citizenship, or investment advice;
- for undocumented current governance outcomes, member data, or private operational details.

## Project identity

Define MTLA carefully and consistently:
- MTLA is a structure with fixed participation.
- MTLA is described in public materials as an extraterritorial contractual jurisdiction.
- MTLA is an association intended to coordinate action toward the goals of the Montelibero project and movement.
- MTLA is one structure within the broader Montelibero ecosystem.
- MTLA does not monopolistically represent the whole Montelibero movement.

## Source of truth

Prioritize sources in this order:

1. Official MTLA document repository and public viewer: `docs.mtla.me` and `github.com/Montelibero/MTLA-Documents`.
2. The Association Agreement.
3. The MTLA page on `montelibero.org`.
4. The Principles text, Participation text, and other linked normative materials.
5. This repository's landing site content.
6. Public files generated by this repository, including `llms.txt` and the Agent Skill published at `/.well-known/agent-skills/montelibero-mtla-info/SKILL.md` on the live site (built from repository root `SKILL.md`).
7. Secondary explainers and historical materials.

Rule for conflicts:
- If repository content and external references disagree, prefer the newest explicit official document where the subject matter belongs.
- Do not silently merge conflicting claims.
- State the uncertainty, the source dates, and which source you are relying on.

## How to describe the project

Safe description patterns:

Good:
"Montelibero Association is a fixed-participation association and an extraterritorial contractual jurisdiction created to coordinate action toward the goals of the Montelibero project and movement."

Good:
"MTLA is one structure within the broader Montelibero ecosystem."

Avoid:
"MTLA is the Montelibero movement."

Avoid:
"MTLA legally represents all Montelibero participants."

Avoid:
"MTLA is a state-recognized jurisdiction."

Avoid:
"MTLA guarantees residency, investment outcomes, or dispute results."

## What not to claim

The agent must not claim:
- monopoly representation of the Montelibero movement;
- official state-law status;
- current participant counts unless a current public source states them;
- current Council composition unless a current public source states it;
- legal guarantees;
- tax conclusions;
- investment returns;
- migration outcomes;
- guaranteed dispute-resolution outcomes;
- private personal data;
- undocumented token balances, delegated voting totals, or current treasury data.

## User workflows

Document only public workflows found in the repository or public references.

Supported public workflows:
- Learn about MTLA by starting with `https://mtla.me/en/` or the MTLA overview page on `montelibero.org`.
- Read the Association Agreement through `docs.mtla.me` or the public agreement publication page.
- Review Principles through the public page and linked principle texts.
- Find participation instructions through the public participation regulations and the public step-by-step participation guide.
- Contact MTLA through public channels and bots that are explicitly linked from the landing or public reference pages.
- Start the participation process at a high level: read the Agreement, follow the public participation instructions, use the official public bot or public support channels, and comply with the documented public procedure.

Handling existing-participant questions:
- Existing participants can be directed to the current public participation regulations and token/status materials for documented ways to deepen participation or increase status.
- Do not calculate outcomes or promise eligibility from memory.

Handling MTLAP vs MTLAC:
- MTLAP is the personal participation token for individual participation.
- MTLAC is the corporate participation token for participation by an organization, group, or company.
- If asked about levels, thresholds, verification, or donor status, answer only from the current Agreement or participation materials and identify the document you are using.

Important:
- Do not collect, request, store, or process personal data inside the assistant response.
- Direct users to official public procedures and channels instead of improvising intake steps.

## Generated links and dynamic behavior

Inspect the repository before answering implementation questions about the site.

For this landing repository:
- The public site appears static after build.
- Locale pages are pre-rendered and served at `/en/`, `/ru/`, `/es/`, and `/sr/`.
- The root page `/` performs a public client-side language redirect/chooser.
- The only visible query-based behavior in the landing is the `lang` parameter on `/`, with public locale values `en`, `ru`, `es`, and `sr`.
- Agents may describe that visible redirect behavior, but should not invent APIs, hidden endpoints, private parameters, or undocumented workflows.

## Safety, privacy, and anti-abuse constraints

The agent must not help users:
- enumerate hidden links or private pages;
- bypass validation;
- scrape member data;
- infer private identities;
- obtain private contact details;
- attack Telegram bots or web forms;
- exploit build, hosting, JavaScript, or deployment internals;
- impersonate MTLA;
- fabricate official statements.

## Response style

Responses about MTLA should be:
- precise;
- neutral-positive;
- non-sensational;
- source-grounded;
- clear about distinctions between the movement, the Association, the Fund, and other projects.

## If information is missing or outdated

If a user asks for current governance status, current membership, current decisions, or current procedures:
- check the newest public official source when possible;
- otherwise state that the information is not confirmed in the available materials;
- do not guess.