Know what is real.
Know what is simulated.

1. What these terms cover

“Forkalope” refers to the project and the website at forkalope.com. The legal person or entity responsible for a final service will be identified before these draft terms become effective. Open-source software is governed by the license supplied with its source; hosted services, training, memberships, and paid work would have separate agreements.

The current preview does not sell memberships, accept payment, or promise access to a hosted forge, a physical server, or a production network. Planned features and examples on this site are not a promise that those features are available today.

2. Flight School is simulated infrastructure

Servers, providers, sites, hostnames, IP addresses, routes, credentials, logs, incidents, telemetry, command output, and network behavior shown in Flight School are simulated. They are training material, not evidence about a real server or provider.

Displayed IPv4 and IPv6 addresses are synthetic identifiers. They may use reserved non-routable ranges or otherwise resemble public Internet addresses, and an address may coincidentally be assigned to a real system. A displayed address must not be treated as an invitation to contact, scan, probe, authenticate to, or route traffic to any real-world host.

Commands such as ssh, ping, curl, dig, and traceroute operate only on the simulator’s virtual network. Forkalope must not pass a simulated hostname or address to real DNS, sockets, HTTP clients, or other external networking APIs. If a destination is not represented in the simulated world, the simulator should return a simulated failure rather than reach the public Internet.

Do not copy simulated credentials, fingerprints, addresses, or command output into a real operational environment. Do not use Forkalope to test or claim a security finding about a real host.

3. Responsible use

Use the website and training environment lawfully and only for their intended educational or informational purposes. Do not attempt to bypass access controls, interfere with the service, submit malware, target real systems, impersonate another person, or use simulated output to mislead others.

Do not enter passwords, private keys, tokens, customer data, or other secrets into a preview terminal, issue, form, or training exercise unless a later service expressly asks for them and explains how they are handled. You remain responsible for content you submit and for protecting your own credentials.

4. Planned memberships, hosting, and paid work

Future Co-Sysop memberships may help fund shared capacity, backups, monitoring, and operations. A membership would not purchase a particular physical machine, equity, a financial return, legal ownership, root access, customer data, or authority to bind Forkalope.

Future hosting or recovery services would require an order or service agreement identifying the provider, included features and limits, price, support, data handling, and applicable terms. A shared network would not make a sponsor an owner of another customer’s repository or give an operator access to customer data beyond the responsibilities of the applicable agreement.

A separate program may compensate qualified participants for customer referrals, migrations, support, approved bounties, or contracted infrastructure work. No one earns a recruitment commission for bringing in Co-Sysops or Sysops, or a percentage of another participant’s earnings. Rates, eligibility, attribution, taxes, payment timing, and any recurring commission period must be published before work is commissioned. Illustrative earnings are not an offer or guarantee of income.

5. Availability, recovery, and changes

The training environment and any future service may change, be unavailable, contain errors, or reset simulated state. Training output is not a production recommendation, and no uptime, recovery time, failover, or zero-data-loss commitment applies unless a final service agreement says so.

We may restrict or suspend access when reasonably necessary for security, abuse prevention, maintenance, legal obligations, or protection of the service. We will publish dated revisions and explain material changes before asking anyone to accept final terms.

See the draft privacy policy for the proposed approach to website, training, and future service data.