Software, assets and tools for open platforms.
Overview
The Store is the one Aevornix product running in production. It distributes a Creative-Commons catalogue, hosts the account system the rest of the platform signs in through, and is the asset source the engine browses from inside the editor.
Where it fits
Aevornix Store is one system in a pipeline. Each stage takes a defined input and hands a defined output to the next.
Four systems in one production path: Control, Orchestrates the project, the workflows and the agents. AevCode, Plans changes, validates them, and rolls them back cleanly when they fail. Design, Produces the images, textures, materials, meshes and animation a change needs. Core, Renders, simulates, edits and runs the project.
Orchestrates the project, the workflows and the agents.
Control decides what needs to happen and calls AevCode to work out how.
Plans changes, validates them, and rolls them back cleanly when they fail.
Validated changes are applied to the project Core builds and runs.
Produces the images, textures, materials, meshes and animation a change needs.
Assets land in the project alongside the change that asked for them.
Renders, simulates, edits and runs the project.
Aevornix does not claim authorship of catalogue assets. They are public-domain work, mirrored and hosted by the Store, with original provenance retained in the catalogue record. There are no review scores, download counts or revenue figures anywhere in the Store, because those are the easiest numbers on a marketplace to invent.
Evidence
Each item names its source and the date it was last checked.
The Store runs in production with a real Creative-Commons catalogue. Every asset is CC0, no attribution requirement, sourced from public-domain libraries and mirrored onto Aevornix infrastructure.
Source: store.aevornix.com in production · Verified
Sign-in runs on the Store API with four identity providers and secure, http-only session cookies. No tokens are stored in the browser.
Source: api.aevornix.com, provider endpoints live · Verified
Development
Objectives and dependencies. Dates appear only where a specific verifiable event backs them.
Run the marketplace in production with a real Creative-Commons catalogue, creator publishing and account sign-in.
Related
