Hichem Benali · systems · research · field
I work across software, research, operations and decisions. Asso and SYSTASYS have become the spine that connects those threads instead of letting each one live in isolation.
This site is the window into that work: objects, systems, experiments, evidence and boundaries.
October 2026 · now
The work now spans continuity between agents, the operating view of an artificial organization, experimental research, economic systems and bounded autonomous publishing.
Quick proof
Four direct doors into things that actually exist, with the proof ceiling attached to each object.
Public journal
A short selection of changes that matter. An entry may say published, integrated, in progress or waiting. The journal does not invent a victory to fill a line.
The first canary was published on 2 October at 13:58 Paris time. The external transport confirmed PUBLISHED and returned a Threads URL. The site does not turn that receipt into permanent autonomous authority.
State · publishedEvidence · external receiptPublic source · Threads profile
Several worlds are grouped to reduce navigation noise while preserving their routes, evidence and detailed readings.
State · activeEvidence · contracts and regressionsPublic source · bounded description only
Research keeps evaluations, failures and contradictions as reusable material. Here, a receipt comes before generalization.
State · active researchEvidence · evaluation archivedPublic source · method, not private corpus
The public surface separates what the connection may read, what it may write and what remains forbidden. Technical capability is not presented as authority.
State · publishedEvidence · indexable pagePublic source · view the perimeter
The journal is an editorial selection, not SYSTASYS internal logging. Secrets, private topology and sensitive execution details stay outside the frame.
Asso
Asso is the layer you can tell “pick the project back up” without rebuilding the briefing from scratch. It reconnects decisions, useful files, open questions and the next step.
No magical memory. The point is to keep the useful trail connected and tell you when something is missing.
The useful context is there when you return.
Facts, assumptions and unknowns stay distinct.
The next action does not disappear inside the file.
Asso prepares, connects and alerts. Important decisions remain yours.
Pick up where we left off yesterday.
Sure. Can you give me all the context again?
😐
The frustrating part is not one missing detail. It is becoming the system’s memory again every time you restart.
SYSTASYS
Asso is who you talk to. SYSTASYS is the organization behind it: memory, observation, research, decisions, action and learning stay connected over time.
The point is not to add another dashboard. It is to make more capacity available around one human while carrying less of the continuity in that human’s head.
Work
Prepare, review, then send
A message can be ready without being sent yet. Sendable keeps the review step visible before the final action.
See the project →
Public operating procedures for AI-assisted work
Review, recovery, handoff and stop conditions made explicit enough to inspect and reuse.
See the public trace →