The Charter of SYMMACHY

Article I — Identity

§1.1 The legal entity, when constituted, will operate under the brand SYMMACHY (pronounced sym-MAH-key).

§1.2 SYMMACHY is defined as an Autonomous Security Infrastructure Company. Its scope is the design, build, deployment, and operation of software, hardware, and operational systems that protect critical infrastructure, AI-native enterprises, and sovereign-adjacent operators.

§1.3 The mission of SYMMACHY is to make autonomous protection legible, lawful, and audit-grade in environments where the cost of failure is measured in lives, sovereignty, or industrial collapse.

Article II — What we will not do

§2.1 Civilian non-deployment. SYMMACHY does not, under any contract, deploy autonomous force-projection systems against civilian populations under non-conflict policing, against migrants outside formal legal asylum or border channels, against protest or assembly suppression, or in support of mass surveillance of populations under autocratic regimes.

§2.2 Refusal of exclusivity. No single customer (including any government programme) may exceed thirty-five percent (35%) of trailing twelve-month annual recurring revenue.

§2.3 Black-box autonomy refusal. SYMMACHY does not deploy any autonomous system whose decisions cannot be reconstructed by a third party from public transparency logs without our cooperation.

§2.4 No deployment without an Authority of Use. Each customer engagement requires a signed Authority of Use document delimiting permitted operations, geographies, threat models, and stop conditions.

§2.5 No offensive systems. SYMMACHY does not build, sell, integrate, or operate offensive cyber or kinetic weapons systems.

§2.6 No model we cannot turn off. Every model in production must have a customer-accessible kill-switch verified in pre-deployment drill.

§2.7 No deployment in active combat operations. SYMMACHY does not deploy systems into theatres of declared armed conflict, nor in support of operations conducted under such conditions.

Article III — How we will be transparent

§3.1 Refused engagements report. The founders publish quarterly to the board and an annual public summary listing every engagement refused, the sector and geography, the principle invoked, and the signing founder. The counter-party is never named.

§3.2 Revoked authorities log. Every Authority of Use revoked by the customer is recorded with date, scope, and the reason given.

§3.3 Annual mission audit. An independent third-party auditor reviews adherence to Articles II and III each year. Findings are published in summary form.

§3.4 Customer evidence portability. The full evidence chain belongs to the customer and is transferable in machine-verifiable form on contract termination.

Article IV — How we will hire, fire, and govern

§4.1 Mission alignment is a hiring criterion, evaluated explicitly and recorded.

§4.2 Founders carry the radio: the founders are personally on-call for every customer P0 incident until the security and operations leads are hired.

§4.3 Equity is meaningful, not symbolic. The first ten hires receive equity in a published band, vesting over four years with a one-year cliff.

§4.4 Compensation is transparent inside the company and published as bands outside.

§4.5 Board composition: founders, an independent ethics director from the Charter ratification onward, and (post Series A) a lead-investor seat. The ethics director holds a published mandate to vote against any contract that violates Article II.

§4.6 Founders retain a veto on any contract that violates §2.1 — a veto that no investor consent can override.

Article V — Acquisition / capital events

§5.1 Pre-committed acquisition criteria: mission preservation, founder lock-up no longer than twenty-four months, valuation at or above industry comparables, no civilian-deployment requirement imposed by the acquirer, and continued operational autonomy for the LATAM organisation.

§5.2 Any IPO disclosure must list Articles II and III as material to the business.

§5.3 No sovereign-fund investment will be accepted that requires Charter violation, present or anticipated.

Article VI — Drift resolution

§6.1 Drift is defined as a four-quarter pattern of decisions that, taken together, depart from Articles II or III.

§6.2 Detected drift triggers a 30-day correction plan, scoped, owned, and reviewed by the ethics director.

§6.3 Two failed corrections trigger Charter review, restructuring, or — if necessary — formal amendment per Article VII.

Article VII — Amendment

§7.1 The Charter is amendable by unanimous founder consensus, or by two-thirds founder plus ethics director non-objection, and only with an Architecture Decision Record published before the amendment takes effect.

§7.2 Articles §2.1, §2.5, and §2.7 are not amendable during founder tenure. They may be amended only by founder departure and replacement under Article IV.