This timeline brings together the formally defined directions for Metnos. It separates delivered work from items that are ready or waiting, so a future specification is never mistaken for an available feature.
The dates show when each direction was defined and, where completion is supported by evidence, when it was implemented. Internal technical specifications, analyses, and architecture decisions are not published.
Local, controllable personal memory kept separate between users. The direction is designed but not scheduled: the current assessment does not yet justify the cost of the complete system.
One deterministic check that keeps executor contracts, arguments, and descriptions aligned across every available language.
An operational guide that uses public documentation and admitted contracts to answer questions without becoming a second planner.
A universal engine that automatically hands long tasks to persistent, traceable, resumable, and governed execution, with no profile for the user to select.
Extends multilingual operation to messages, manifests, detection vocabularies, planning, prompts, and Tutor, with automatic completion of the language selected for the instance.
Certification across 24 golden flows in Italian and English. It measures interpretation, planning, authority, effects, recovery, and response over two complete cycles, using an oracle independent from the system under test.
Reading the status. “Completed” requires evidence in the distributed system. “Ready” marks a defined direction that is not yet available in full. “Waiting” means there is no implementation commitment.