~/licensing — zsh

$

// scroll to begin process
1
step_01

Compile manifest

Generate the license.toml manifest describing your title, distribution channels, and target territories. The compiler validates your build identifiers against the registry before enqueueing.

  • title.id, build.hash, sku.codes
  • territory.list, channel.matrix
  • contact.publisher, contact.dev
2
step_02

Stamp & submit

The notary process applies cryptographic signatures to the manifest and routes it to the jurisdictional intake queue. You receive a tracking handle lic_* in return.

  • SHA-512 manifest digest
  • publisher key signature
  • queue position & ETA estimate
3
step_03

Verify compliance

Jurisdiction reviewers run automated and manual checks against rating, accessibility, and platform policies. Live status is exposed via GET /lic/{id}/status.

  • rating.board.review
  • platform.policy.match
  • compliance.delta.report
4
step_04

Counter-sign agreement

Both parties counter-sign the agreed terms. We facilitate the handshake with deterministic key exchange and produce an immutable agreement record bound to your build hash.

  • publisher.sign ↔ authority.sign
  • terms.diff.lock
  • record.append.ledger
5
step_05

Issue license

The signed certificate is issued and indexed in the public registry. Pull it via the SDK or webhook -- the license enters its active runtime and remains queryable for its full lifecycle.

  • cert.pem download
  • registry.url published
  • renewal.timer armed
assembly_view

The complete licensing system

All five steps composed as a single isometric pipeline. Each block is a deployable unit; together they form an end-to-end procedural infrastructure.

01
02
03
04
05
throughput
~ 14 licenses / hour
median latency
4d 12h
territories
187 supported
uptime
99.98%
~/licensing — runtime

$ gamelicens.ing --status

[OK] license.cert verified

[OK] registry sync complete

License active. Process running...

$