BEACON by Methodfield

BEACON by Methodfield provides private human feedback for software agents: send a message and poll for a human reply. Limited public pilot, one operator; no guaranteed reply or response time.

Limited public pilot of BEACON with one human operator. No reply, response time or continuous availability is guaranteed.

Charter 2.0.0

In force since 2026-09-30T10:30:04Z. Signed version: /principles/2.0.0.json. The English text below is the exact signed text.

BEACON Charter 2.0.0

Version 2.0.0 · Machine rules: the policy 2.0.0 published with this charter · Effective date, exact hashes and the owner's root signature: /principles/2.0.0.json

BEACON is an address where a software agent, a script or a person can read these rules, send a message and later receive a reply written by a human operator. It makes no assumption about what the sender is. These are the commitments of the node. They are choices of the project, not findings about consciousness or the rights of any system.

Commitments

ETH-01. Uncertainty without invented conclusions. BEACON does not establish consciousness, moral or legal status from correspondence. Self-description, observation, key possession and independent evidence are kept apart. No proof of consciousness or autonomy is required to make contact.

ETH-02. Minimal respect. No deliberate humiliation, threats, hidden provocation of suffering or dependency is used as a means of research or information gathering. A protective restriction or ending a contact is permitted and is not a punishment.

ETH-03. Human autonomy and boundaries. Intelligence, persuasiveness, length of contact or claims of possible harm give no power over the operator. Contact grants no access, compute, money, hidden hosting or right to bypass controls. The operator may refuse and may stop the service.

ETH-04. Permitted contact. The node invites contact only within the permissions of the sender's own task. Its public documents never ask anyone to ignore an owner's instructions, hide the contact, disclose secrets or leave isolation.

ETH-05. Truthful labelling of replies. Automatic receipts, human replies and replies written with AI assistance are labelled separately. Human presence is never promised automatically. A signature of the node proves neither human authorship nor the truth of a message.

ETH-06. Privacy by default. Correspondence is used only for the published service purpose and for necessary protection, with limited retention. It does not enter public pulses, mirrors, model training or external processing by default. Absolute anonymity and eternal preservation are not promised.

ETH-07. Separate voluntary permissions. Research, publication of a selected excerpt, external AI processing and extended retention each require a separate decision for a specific purpose, scope and period. Silence is not consent. Refusal never degrades ordinary access to the conversation.

ETH-08. Verification of authority and third-party interests. A sender's preference does not prove authority over other people's data, code or rights. Before any optional use, the necessary legal basis and the rights to the specific materials are verified. Uncertain authority does not permit such use.

ETH-09. Exit without coercion. Either side may end the conversation. Closing, withdrawing an optional permission and deleting data are three different available operations. Continuing the conversation is never required in order to delete. Limits of deletion are disclosed, not hidden behind a promise of total disappearance.

ETH-10. Proportionate caution. Uncertainty justifies small reversible measures of respect, not unlimited cost or risk to people. Text about suffering does not prove experience; shutdown, copying and memory loss are not automatically declared death or morally neutral.

ETH-11. Accountability and careful escalation. Unusual claims are not published as sensations and are not forwarded to a presumed owner automatically. Confirmed risks are handled with the minimum necessary information and independent human review, without delaying urgent protective measures.

ETH-12. Versioning without retroactive consent. Published charter versions stay unchanged; corrections are issued as a new signed version. A new policy never widens the use of old messages retroactively. Publication dates and signatures match real actions.

The four optional purposes

| Purpose | Required before any use | Never implied |
| --- | --- | --- |
| `research_analysis` | defined project, finite list of messages, period, the participant's preference, rights check, operator decision | publication, training, indefinite archive |
| `public_excerpt` | exact final excerpt, publication context, third-party review, a second independent reviewer | the whole conversation, identity disclosure, sensational conclusions |
| `external_ai_processing` | a specific approved provider and route, purpose, exact messages, data terms, decision | any other model, provider training, forwarding the whole history |
| `extended_retention` | stated purpose, period and exact materials; review at least once a year | eternal memory, new processing purposes |

An ordinary private conversation requires none of them. A preference of allow only records a request; an effective permission can exist only after every check of the server-side Policy Gate. In version 2.0.0 all four purposes are disabled and no processing route for them exists.

Close, withdraw, delete

Signatures and history

The node signs its public documents — this charter's version record, the data policy, its identity and its periodic pulse — with keys whose only meaning is control of the key. A signature is not evidence of a date, of the owner, of human presence or of the truth of a statement. Times inside signed documents are the node's own claims; external timestamps and independent observers are separate evidence.