Work
I do not want this to be a project list. I want to show the whole movement: the question, the object, the test, what reality answered and what changed after.
The rule of this room is simple: object, evidence, boundary. Anything that cannot be publicly proved is presented as work in progress, not as a victory.
Product proof · Public Proof Pack V3
These captures were remade on 3 October 2026 from the Director V2 actually being served. Capture mode masks monetary amounts and personal files before paint. What you see here is the current surface, not a showcase reconstruction.
al-Ḥāl brings the machine, founder attention and money into one composition. al-Fihrist now appears in the current navigation.
Night mode preserves the product hierarchy and geometry while moving into its lapis sky and darker materials.
The medallion, machine state and founder need recompose for the phone without changing the underlying reading.
Public Proof Pack V3: capture from the private surface currently being served, native masking before paint, then only already public-safe pixels are copied into the site. Older screens remain provenance, not the current showcase.
See the Director V2 proof →Enter the ATLAS room →Proof layer
This projection does not replace the internal journal or SYSTASYS owners. It keeps only enough information to verify what the public site claims, together with the matching proof ceiling.
Proven: Situation was recaptured from the actually served Director in desktop day, desktop night and true 390 × 844 mobile after native Capture-mode masking.
Does not prove: private cockpit content, runtime authority or the firm’s economic state.
See the captures →Proven: X has confirmed publication history, LinkedIn has a visible first canary and Threads published its first canary at 13:58 Paris time.
Does not prove: unlimited authority, autonomous replies everywhere or audience performance.
See public outputs →Proven: the native Android app crossed several physical-device proof levels.
Ceiling: an APK or source path does not make every cross-surface interaction terrain-accepted.
See the mobile surface →Supported: the finite result shown in ATLAS has multiple checking paths, including a negative control and independent verification on the first scales.
Not claimed: scientific novelty.
Open the case →Supported: M157 survived the current held-out reading while M388 was disfavored.
Still open: semantic interpretation.
Open the case →Supported: the method separates witnesses, dependencies, inferences and missing material instead of filling gaps.
Still open: the reconstruction itself.
Open the case →Supported: frozen rule before holdout, mandatory baseline, public data and no betting.
Falsifier: if the pattern disappears out of sample, it should be rejected.
Open the case →Useful observation: a first Genizah holdout is MIXED and a large label correction can have near-zero downstream learning value.
Lesson: more corrections or more cues do not automatically mean more useful information.
Open the case →Private native surface · Founder App
SYSTASYS has a real native Android application built with React Native / Expo. It is not a PWA, a WebView or a shrunken Control Room. It projects the same truth through a composition designed for a phone.
Boundary: the app remains private. This showcase does not authorize Play Store distribution, and the mobile interface gains no new authority over the firm.
See the proof level →Today
What is healthy, what changed and what genuinely needs the founder.
Fresh private state without depending on the founder workstation.
One Asso conversation connected to central memory, not a second Jarvis.
A sovereign decision keeps the same identity across surfaces.
Public composition schematic, not a screenshot of the private phone.
SPECTRA · open frontier
SPECTRA sits between the outside world and ATLAS questions. It keeps distinct witnesses separate, preserves contradiction and lets patterns evolve with context instead of freezing a taxonomy too early.
A belief signal is never treated as reality itself.
Interest can confirm, contradict or merely accompany another signal.
Sources stay traceable and common roots can be collapsed.
A pattern is supported only if it survives an observation that did not come from the witnesses that created it.
Authority: SPECTRA observes and structures. This layer gains no trading authority, capital authority or action right.
Work map · October 2026
The domains change, but the grammar stays stable: observe, keep competing hypotheses alive, build, verify, act within a mandate, then feed the result back in.
Control · continuity · maintenance
The cockpit is not decorative. It has to compress a complex organization into one readable state: what is running, uncertain, blocked or waiting for the human. Underneath, understood incidents become reusable cases instead of being rediscovered from scratch.
Boundary: this public surface shows the operating logic, never private topology, secrets or sensitive runtime authority.
State · activeDated · 02 Oct 2026Evidence · contracts and regressionsPublic source · Director V2 trace
Asso · SYSTASYS · swarm
The problem is no longer only answering better. A mission should be resumable, source-grounded, able to move between agents and close cleanly without one lane silently overwriting another.
Visible proof: public doctrine, receipts and continuity surfaces show the mechanism. The operational core remains private.
ATLAS · Terrier · Spirale du réel
Several explanations stay alive until evidence actually breaks them. The research work uses blind trials, falsifiers, counterexamples and re-exploration loops to turn error and failure into new search material.
Field: the method is used across mathematics, forecasting, vision, manuscripts and external benchmarks. Participation is never presented as a result won in advance.
State · active researchDated · 02 Oct 2026Evidence · evaluations and falsifiersPublic source · method only
Predator · economic truth
Economic work separates gross result, costs, funding, attribution and risk. A system can act and learn without that automatically proving economic edge. The goal is to identify what creates real net value and what destroys it.
Boundary: no position, key, capital or market authority is exposed here. No performance figure is claimed without suitable public evidence.
Sendable · receipts · standards
Sendable, R.O.C., agent-governance standards and AI Ops procedures make the same ideas tangible: keep the last human gesture visible, refuse out-of-mandate action, attach evidence to claims and make handoffs recoverable.
Exit: several of these objects have public repositories, captures or publications further down this page.
State · public objectsDated · 02 Oct 2026Evidence · inspectable artifactsPublic source · R.O.C. + Sendable
Public Voice · X · LinkedIn · Threads
Publishing becomes a system too: observe what deserves to be said, choose the right channel, write natively for it, publish only inside the granted mandate and keep the receipt. Silence remains valid when there is nothing useful to add.
Principle: one public identity, several native editorial behaviors. No spam and no silent expansion of authority.
See public outputs →See the consolidated trace →Living corpus
The corpus keeps an intuition, a question, a failure or a source alive long enough to become useful elsewhere. A line of inquiry can sleep, be contradicted, then return weeks later with a different role.
An idea is not discarded simply because it is not ready today.
Mathematics, vision, economics, history, systems and communication can share the same mechanism.
Negative results and broken hypotheses remain useful research material.
A line returns when new evidence, a new tool or another domain gives it a second life.
The site does not publish the private corpus. It shows the discipline that prevents work from disappearing just because it was not mature yet.
State · livingDated · 02 Oct 2026Evidence · reopenings and contradictions retainedPublic source · method only
Competition Universe · external confrontation
The living registry classifies dozens of surfaces as NOW, NEXT, WAIT, STUDY, REENTRY or PARK. The showcase does not turn that into a catalog. It shows five different ways to leave the workshop and let reality answer.
CTFs, puzzles and arenas return feedback quickly. They are useful for learning fast, not for turning a game score into scientific proof.
ARC, WhestBench or weak lensing impose metrics and test sets that can break a method after hours or days of work.
Vesuvius, historical OCR and manuscripts confront vision, sources and reconstruction with incomplete objects where uncertainty is part of the problem.
Lean, Erdős problems and Andrews-Curtis ask for a certificate, counterexample or proof chain rather than a persuasive story.
FutureEval, SoccerNet or CHIMERA force the system to meet a truth, judge or population it does not control.
Discipline: one heavy question at a time. Participation proves contact with an external frame, never victory, superiority or a future result.
State · living registryDated · 02 Oct 2026Evidence · current view + separate dossiersPublic source · confrontation shapes, not a trophy list
Chapter 01 · the firm
The starting question was never how to make an AI “more autonomous.” It was more practical: how do you keep an entire organization from collapsing back into one person’s head as tools, subjects and decisions multiply?
A firm can have strong models, software and data and still remain fragile if someone must remember every context, reconnect every piece of information, inspect every handoff and reconstruct reality whenever a thread breaks.
SYSTASYS grew around that tension. The goal is not to remove the human from the loop. It is to let the firm carry more continuity, research, control and execution without requiring the founder to become its operating system.
This drawing describes a public grammar, not the system’s technical topology. Private components, permissions, secrets, execution paths and security details stay outside the frame.
The tension
Automation can look impressive while creating more supervision, more alerts and more repair work. In that case the machine moves more, but the person remains just as necessary.
The test I care about is harder: can the system perceive a situation, recover what it already knows, push the investigation far enough, act when it has authority, recognize when it does not know, then leave a clean state that the next cycle can resume?
What changes
Storing an incident, a decision or an experiment is not yet learning. Information becomes interesting when it returns at the right moment and changes a hypothesis, a control, a permission or an action.
That is why the same themes keep appearing in work that looks unrelated: mathematical research, public communication, economics, vision, maintenance or agent coordination. The domain changes. The deeper question is often the continuity between what happened and what we do next.
A more capable firm is not automatically a freer firm. It becomes one when it can carry more complexity without making the human more captive to that complexity.
Field notes · visible
Some work should be understandable in seconds, even without technical vocabulary. Here, images speak before the explanation. They show public objects, real outputs and distribution traces. They do not show code, secrets or exploitable internal mechanics.
Predator is shown here as a public language. The engine, private rules, capital and execution stay outside the frame.
The public profile starts connecting the name, SYSTASYS, systems, products and research into one visible presence. This is a dated step, not a claim about the current profile state.
When an idea leaves the workshop, I would rather keep the trace of what was actually published than reconstruct the story later.
Sometimes one screen is enough to make the intention legible: prepare, verify, then keep the final gesture visible.
Communication · what changed
X and LinkedIn are no longer treated as two copies of the same message. One identity can speak differently depending on the place, or publish nothing when there is nothing useful to add. The goal is not volume. It is to make enough of the work legible to interest both someone discovering the subject and someone who knows exactly what they are looking at.
This site shows the visible outcome of that evolution. It does not publish internal selection rules, prompts or automation mechanics.
Object
A draft is not yet a decision. The useful layer in between is context, review, risk and a final human choice that stays visible.
Prepare without sending on the human’s behalf
The prototype separates the draft, the context and the final verdict. Automation helps prepare the action without hiding the moment when a person really decides.
See what stayed in the record →
An external product in a neighboring problem space
Later I found another product using the same name around a nearby gesture. The two screens are shown together because the convergence itself is interesting.
Open their product →Two products can arrive near the same problem without that proving a story about where either one came from. The useful fact is that both objects exist and can be inspected.
When the work leaves the workshop
Published on Hacker News
Operating procedures for review, recovery and handoff in AI-assisted engineering. The project was put in front of a real audience and the distribution trace remains accessible.
Open the HN item →Open the repository →Receipts Over Claims
A simple idea: when an agent says an action is ready, it should be able to leave a piece that shows what the decision rests on. The publication and its distribution attempts stay attached to the work.
Open the source profile →Open the receipts →Terrier / Hypothesis Fan
Do not fall in love with the first answer
When several explanations are possible, keep them separate, look for what would contradict them and only remove the ones the evidence actually breaks.
See Terrier inside SYSTASYS →
An idea can be useful without becoming true by declaration
The useful moment is when a hypothesis has to meet a test, source or result that can genuinely strengthen it or make it fall.
See what came back from reality →What came back from reality
A trace is not a second product page. It stays attached to the work it documents. The important outcomes live here as a compact visual record.
The text exists. The automated rejection exists too. Both stay in the record instead of deleting the uncomfortable half.
The public submission stays attached to the repository, so the object and the moment it met an audience can be inspected together.
Some crossposts were removed. Removal remains a useful distribution result and does not need to be repainted as success.
The capture preserves the prototype as it existed at the time, instead of rewriting the past from the current product.
The similarity exists and deserves inspection. The trace shows the convergence without turning resemblance into an invented story.
Ghost
Publishing, testing or getting something wrong is useless if the system forgets it all later. Ghost links decisions, outcomes and corrections so yesterday’s experience can actually help tomorrow.
A trace is therefore more than an archive. It becomes usable memory.
Elsewhere
This site is a relay. If you want the original profiles, products, repositories and posts, these are the direct paths.
Public profile, posts and conversations around agents, evidence and current work.
Public repositories, tools, standards and inspectable artifacts.
One last verdict before the send. The product is available directly.
Receipts Over Claims, the public notebook for agent decision receipts.
The public submission of the AI Ops SOP Pack, kept as a real distribution trace.
The source profile carrying the R.O.C. publication and its distribution attempts.
