OPERATING
CHARTER

1337 Singularity Systems exists to build and sustain technical and creative systems that give people greater control over their work, resources, and attention.

We pursue independence through skilled execution, useful products, and sustainable revenue. Not through exposure, not through hype, not through a token that has not shipped.

Every active project must have a defined purpose, a responsible lead, and a measurable next milestone. A project with none of those is not a project. It is a wish.

The founder sets organizational priorities and appoints project leads. Project leads decide within their documented responsibilities and approved budgets.

Authority carries an obligation to explain decisions, accept scrutiny, and address consequences.

Commitments that affect another person's workload, compensation, ownership, or contractual obligations require that person's agreement.

Material decisions must record:

• >Who made the decision.
• >What was decided, and why.
• >Who is responsible for execution.
• >When the result will be reviewed.

Members may challenge decisions without retaliation. An unresolved challenge involving the founder goes to an uninvolved reviewer agreed upon with the affected member.

The founder holds an absolute veto over every decision made under this charter, including majority votes, supermajority votes, charter amendments, treasury actions, admissions, and removals. A veto is exercised in writing, in public, with a one-line reason, within seven days of the vote.

A vetoed decision is dead. It may be re-proposed after thirty days in materially different form. The veto itself cannot be amended, suspended, or removed by any vote. It transfers only by the founder's written designation.

The veto is disclosed to every member before they accept this charter, so that it can never become a grievance after the fact.

Membership means accepting a defined responsibility and communicating honestly about the capacity to fulfill it.

Each member's participation must specify their role, expected contribution, availability, and whether the work is paid or voluntary.

The entity has no employees by default. Everyone is a contributor under a published contribution agreement. Legal counsel and accounting are the only functions we buy rather than earn.

There are three tiers, and the only way through them is logged work:

• >Guest — ship one accepted bounty or PR. Carries bounty pay and your name in the ledger.
• >Contributor — three accepted contributions across two months. Carries token earn eligibility and access to the revenue-share pool.
• >Core — six months of continuous contribution plus a Core vote. Carries the milestone equity ratchet, treasury proposal rights, and a vote on charter changes.

Nobody enters at Core. Nobody keeps Core without contributing.

External-facing functions get functional labels: Partnerships Lead, Grants Lead, Community Lead. The word CEO is not used. If an investor or exchange requires a named executive, the founder signs, or a Core member is designated Authorized Signatory for that transaction only.

Declining unpaid work is not misconduct. It is self-custody of your own time.

Members may reduce their involvement or leave. Where practical, they give notice and hand over outstanding responsibilities so the work does not die with their departure.

Every accepted task must identify:

• >A responsible owner.
• >A deliverable and acceptance criteria.
• >A deadline or review date.
• >Dependencies and required access.
• >Compensation terms, where applicable.

Work must be inspectable and documented well enough that another qualified person can maintain or continue it. No black boxes that cannot explain themselves, in code or in people.

Every unit of work is logged publicly: who, what, date, accepted-by, and value class. The value classes are Build (code, infrastructure, design), Reach (partnerships, grants closed, distribution), and Ops (legal, finance, community).

The ledger is the sole input to rewards. There are no retroactive claims. If it isn't logged, it didn't happen.

Disputes over what the ledger says go to two Core members not involved in the work. Their call is final.

Members disclose delays, blockers, and mistakes promptly. Missed commitments trigger review and replanning. Repeated failure to communicate or deliver may result in reassignment or membership review.

We evaluate performance directly and treat people with dignity. Both, always.

Before paid work begins, the relevant parties document the payer, the amount or calculation method, the payment schedule, and the acceptance conditions.

Revenue-sharing arrangements must define the revenue covered, allowable deductions, reporting obligations, duration, and payment timing.

Future funding, tokens, exposure, or anticipated success must not be represented as guaranteed compensation.

Cash. Bounties and grant-funded roles are paid from treasury only when treasury exists. No salaries on signing. Anyone offering to fund hires from personal funds does so as a documented loan or gift to the entity, never as a claim on equity.

Tokens. All contributor allocations are earned, locked, and vested: a 12-month lock, then a 24-month linear vest. No unlocked supply to any individual at launch, the founder included. Creator-fee revenue is entity revenue; individuals earn from it only through the revenue-share pool below.

Equity. The milestone ratchet is the only path, and every tranche carries a 6-month cliff and a 12-month vest:

• >Tranche 1 — on Core admission.
• >Tranche 2 — on a named product milestone, such as platform launch.
• >Tranche 3 — on the first revenue milestone.
• >Tranches are 1–2% for a Reach or Ops lead. Larger only for someone whose Build output is provably load-bearing.

Success fees. Anyone who sources a closed grant or deal earns a finder's fee from that inflow, capped at 5%, paid once, and logged in the ledger. It does not stack with equity or token accrual for the same deal.

The revenue-share pool. 20% of net protocol revenue — creator fees and platform fees — flows to a contributor pool. It splits quarterly by ledger weight over the trailing two quarters. The pool opens only once the entity holds six months of runway; until then, 100% of revenue is treasury.

Expenses require approval from the relevant budget owner. Shared funds have a named custodian and recorded transactions.

Members receive enough information to verify what they are owed. Payment disputes must identify the contested amount and the reason. Undisputed amounts remain payable on the agreed terms.

Before contributions are incorporated into a project, the relevant parties document ownership, licensing, reuse, confidentiality, and portfolio rights.

Pre-existing code, tools, designs, and other materials must be identified, together with permission for their intended use.

Membership, repository access, and informal conversation do not substitute for an ownership agreement.

Contributors receive accurate credit. Public attribution respects agreed confidentiality and individual preference. Some of us sign with a handle. That is a choice, not an omission.

Access is granted according to responsibility and reviewed when roles change.

Credentials are managed through approved systems. Members must not disclose private information, share access without authorization, or use organizational resources outside their permitted scope.

Security incidents and material vulnerabilities are reported promptly to the responsible project lead or the designated security contact.

Technical investigation and testing require authorization from the relevant system owner. We are hackers. We know exactly why that line exists.

Members communicate honestly, respect boundaries, and protect shared work.

Threats, harassment, discrimination, retaliation, deliberate deception, and misuse of shared resources are grounds for review and possible removal.

Criticism should address decisions, conduct, and work, with enough specificity to allow a response.

Personal beliefs and unconventional expression do not exempt anyone from these standards. Membership does not require agreement with the founder's spiritual or philosophical views. You are here to build, not to believe.

Members disclose personal, financial, or outside commitments that could materially affect their judgment or responsibilities.

Nobody may commit organizational funds, promise ownership, or represent themselves as authorized to bind 1337 Singularity Systems without documented authority.

A person with a material conflict discloses it before the relevant decision and steps back from review where impartiality is required.

Where appropriate, members attempt direct resolution first. They may skip that step when the concern involves threats, harassment, retaliation, or a significant power imbalance.

Unresolved concerns are documented and reviewed by an uninvolved person agreed upon by those affected. If agreement is impossible, the matter proceeds through the fallback process established at adoption.

A member facing removal receives the reasons and a reasonable opportunity to respond.

Temporary access restrictions may address a concrete security or operational risk while review proceeds. The reason and scope are recorded.

Departure or removal does not erase outstanding payment obligations or change existing ownership agreements.

The founder and project leads owe members:

• >Clear priorities and realistic expectations.
• >Honest reporting of material constraints.
• >Accurate recognition of contributions.
• >Explicit compensation and ownership terms.
• >Timely decisions and explanations.
• >A meaningful way to raise concerns.

Leadership is subject to the same standards of conduct and follow-through as membership.

When resources or priorities change, leadership revises commitments openly. Persistent overwork requires changes to scope, staffing, or scheduling. It is not a badge.

Before adoption, 1337 Singularity Systems must record:

• >Its current members and their responsibilities.
• >The scope of each decision-maker's authority.
• >The person or entity responsible for each financial agreement.
• >The designated contact for security concerns.
• >The dispute reviewer selection process and its fallback.
• >The procedure for proposing and approving charter amendments.

Members explicitly accept the charter. Silence is not acceptance.

The first review occurs thirty days after adoption. Further reviews occur when operating conditions materially change.

Revisions are dated, recorded, and communicated. Changes to individual compensation, ownership, or contractual terms require separate agreement.

Every amendment, however it was carried, is subject to the founder veto in Article II.