THE DARK FARM
Altineris operates a second distribution path that does not ask the platform for permission. It exists because reach through the sanctioned interface alone is slow and capped, and it is in scope by our decision rather than because any evidence says it is safe. This page says what it is, what we do not claim about it, and the five documented ways it can fail.
WE PUBLISH THIS BECAUSE THE ALTERNATIVE IS A SITE THAT IMPLIES A BOUNDARY WE DO NOT HOLD. EVERY OTHER PAGE HERE MARKS WHAT IS BUILT AND WHAT IS NOT; THIS ONE MARKS WHAT IS RISKED.
PROHIBITED, PERMITTED, AND NOT CLAIMED
What the code may not do
No dependency on a browser-automation or scraping-framework stack. No addressing the platform's private mobile endpoints, and no sending of their headers. This boundary is enforced by a test in the build, and it is the only part of this page a guard covers.
What it does do
Parsing and ranking third-party material taken from the platform's public surface, for competitor research. Operating a fleet of real devices and real accounts, under named operators who have signed for the risk.
What we will not pretend
That this material comes from a sanctioned source — it does not. That the countermeasures work. That the fleet is safe. Nothing on this page is an assurance, and we would rather say so here than be found out later.
WHAT WE ARE ACCEPTING, IN ONE PLACE
These are read out of the platform's own published terms and enforcement behaviour, not from our hopes about them. Documented means the platform says it.Unknown means no source available to us gives a number, so we do not invent one.
| # | What is accepted | Basis |
|---|---|---|
| 01 | The fleet is one position, not ten. Enforcement propagates across anything the platform can link, so it can be lost together rather than one at a time. | DOCUMENTED |
| 02 | Replacing a removed account is a fresh violation, not a repair. Rotation compounds the position rather than resetting it. | DOCUMENTED |
| 03 | Driving a device over a debug connection carries a two-strike ceiling that no amount of pacing moves, because the trigger is the access method itself, not the behaviour. | DOCUMENTED |
| 04 | The research half carries legal exposure to the operator personally, not only to the accounts. | DOCUMENTED |
| 05 | Near-identical posts published across a fleet meet the platform's own spam definition on its plain wording. We do not read that wording as being on our side. | DOCUMENTED |
| 06 | The probability of any of the above is unknown. The one number this decision needs — a rate at which fleets are actually lost — does not exist in any source available to us, and the countermeasures have no evidence behind them. | UNKNOWN |
THE DECISION RESTS ON THE JUDGEMENT THAT THE EXPECTED RETURN JUSTIFIES LOSING THE FLEET. IT DOES NOT REST ON THE COUNTERMEASURES WORKING.
A DISCLOSURE, NOT A MANUAL
Our own documents contain precise values for nearly every threshold the platform leaves undefined — pacing schedules, request ceilings, posting progressions, and a full table of transformation parameters. None of it appears on this page and none of it will.
Because those numbers are ours, not theirs
Every one was read out of our own code. That establishes what our software does. It establishes nothing whatever about what the platform does, and publishing it would dress a measurement of ourselves up as knowledge about them.
Because stating a risk is not teaching a technique
Saying that we accept a position is disclosure. Publishing the recipe is something else, and it is not what candour requires of us. Any document here that states a numeric threshold for platform enforcement is fabricating it — including ours.
| Capability | State |
|---|---|
| Account register, health and integrity tracking | IN THE REPOSITORY |
| Squad isolation — one budget per group, never pooled, so one loss is contained | IN THE REPOSITORY |
| Device and environment control | IN THE REPOSITORY |
| Credential lifecycle, alerting and log redaction | IN THE REPOSITORY |
| Operator register, access and signed risk waivers | IN THE REPOSITORY |
| Variation engine — producing distinct cuts across a fleet | IN THE REPOSITORY |
| Operating at scale | ONE DEVICE, TESTING |
| A measured loss rate | DOES NOT EXIST |
IN THE REPOSITORY MEANS MERGED WITH TESTS. IT DOES NOT MEAN RUNNING, AND IT DOES NOT MEAN SAFE. THE SANCTIONED PATH IS DESCRIBED IN THE AEGIS, AND IT IS THE ONE WE PREFER WHENEVER IT REACHES.
IF THIS PAGE CHANGED YOUR MIND
That is a reasonable response and we would rather have it now than after a contract. The rest of the system stands on its own — the generation engine and the publishing gates are the parts we are proudest of.
SEE THE SANCTIONED PATH