Public evolution log · evidence-backed

Not a history of promises.A trace of product evolution.

A young domain does not by itself show how much work has happened. This page publishes a selective, evidence-backed MetaCore evolution log: preserved manifests, audit checkpoints, public endpoints, PILOT stages and clearly labeled historical statements.

LIVE public logFormat selective, not every commitJSON /changelog/releases.jsonEvidence SHA256 + public surfaces
01 · EvidenceA claim should leave a trace

Where possible, a release entry is tied to a manifest, audit digest, deployment receipt or public endpoint.

02 · BoundariesHistory ≠ technical proof

Year-level project history is labeled separately and is not presented as evidence with the same weight as a hashed artifact.

03 · ContinuityRollback and manifests over mythology

The evolution log is grounded in real checkpoints, not in an attempt to make the project appear older.

Release history

Evolution timeline.

The log starts with entries for which we have sufficiently clear server-side or public evidence. Older history will only be backfilled when its sources are organized and verified.

2025HISTORYDECLARED_HISTORY

MetaCore enters its public project phase

MetaCore begins to be presented publicly as a distinct product direction combining accumulated Human Systems know-how with AI systems evolution.

Year-level historical statement. The exact first public release archive has not yet been linked into this log.
2026-09-07RELEASESERVER_ARTIFACT

Platform identity and market-claim hardening

The public layer locked the category “Persistent AI Operating Platform”, defined MetaCore OS as an Operating, Context & Control Layer, and tied business claims to scoped authority, approval gates and price authority.

2026-09-16RELEASEVERIFIED_ARTIFACT

Package-content integrity + MetaCore Brand V2

Codex50 and MetaCloud package content was moved with 1:1 content checks; Brand V2 was marked ACTIVE_VERIFIED with verified light/white marks and the canonical “Human–AI. Real Progress.” tagline.

2026-09-18RELEASESERVER_ARTIFACT

MetaCloud public surfaces expanded across languages

A documented generation and restore path was recorded for MetaCloud public pages in LT, EN, RU, FR, PL and DE, including explicit rollback documentation.

2026-09-19PILOTDEPLOY_RECEIPT

The new MetaCore panel enters PILOT

panel.metacore.lt started as a parallel new interface shell. The deployment receipt explicitly records that the existing /activate/app/ environment, application code and database were not modified.

2026-09-20RELEASELIVE_PUBLIC_SURFACE

Public trust hardening: maturity, team, creator path

A unified LIVE / PILOT / LAB / ROADMAP vocabulary, a public “Who builds MetaCore” page, a creator/concept DELTA contact path, and this evidence-backed evolution log were added.

Evidence layer

The text is not the only inspectable layer.

Alongside the human-readable changelog, we publish a machine-readable release feed and sanitized evidence JSON. Private server paths and sensitive internal information are deliberately excluded.

Machine-readable log

The public JSON feed can be read by people, search engines or external AI evaluators.

https://metacore.lt/changelog/releases.json

Found a mismatch or have an older verifiable source?

This changelog is not decoration. If you have a concrete release artifact, archived copy, manifest or another inspectable source, the timeline can be extended without overstating history.