Infrastructure 04 of 06
Lanvex Store
Controlled publication: company qualification, product review, signing, licensing and the customer-approved installation that follows.
In development
What it enables
- A reviewed route to customers for first-party and independent frameworks on the same terms.
- Two distinct review tiers, so a customer can tell a baseline review from a deeper audit.
- Signed releases, with both the publisher’s signature and Lanvex’s, and a recorded lifecycle for updates, rollback and revocation.
Who it serves
- Publishers seeking a route to market.
- Customers and their administrators, who decide what installs on their own machines.
- Reviewers applying one published standard rather than a private one.
Scope and boundaries
- Qualifying a company and reviewing a product are separate gates, and passing one is not passing the other.
- A security review and a domain dossier answer different questions, and each listing shows which has been done.
- No reserved domains. Independent publishers may compete with Lanvex’s own frameworks, including in accounting and software development.
- Placement follows what customers choose, not who built it.
In practice
- A publisher submits a framework with its manifests, declared permissions and tests; review is recorded against a published standard.
- A customer administrator refuses an update; it does not install.
- An offline site keeps running on previously accepted state, with revocation rules written for that case rather than pretended away.
Where we are
Upcoming. The review standard, the signing process and the publisher terms are being settled first, so the first listings arrive with the rules already public.
Questions
- Can a student project be sold here?
- Not as it stands. Commercial publication needs an enrolled company and a reviewed product. A sandbox build is not a released one.
- What are the two tiers?
- Reviewed is the baseline. Sovereign Certified is a deeper audit, repeated yearly, and a publisher chooses whether to seek it.