Human context first
Model the real job a person is doing, not the database table they happen to touch.
PAJIC SYSTEMS / PRODUCT FAMILY
Systems for the
Systems for the
real world.
Software for operations where timing, identity, authority and trust actually matter. Each product is deliberately its own world.
Four products.
Four different jobs.
AVIATION OPERATIONS01
CrewCloud
A crew operating system for roster, duty, logbook, Intercom, compliance and airline operations.
MIA → JFK
DIGITAL IDENTITY02
pajID
Passkeys, OIDC, scoped consent and selective disclosure for services that should not collect everything.
only share what is needed
SERVICE OPERATIONS03
Oleta
Headless availability, resources, holds and reservations behind any frontend you want to ship.
POST /booking-holds201 CREATEDCREDENTIAL INTEGRITY04
Ocala
A provenance and trust model that explains issuer, signer authority, lifecycle and proof.
issuer → signer → proof
HOW IT CONNECTSIndependent products.
Independent products.
Compatible instincts.
CrewCloud can use Ocala without becoming Ocala. Oleta can power a wildly different frontend without becoming that frontend. pajID can prove identity without becoming the application.
Different products.
Same intolerance for fake clarity.
Explicit trust
Authority, provenance, consent and permissions should be inspectable facts.
Real contracts
Versioned APIs, standards and data boundaries are product features, not backend trivia.
No fake status
If a release, verification state or artifact does not exist yet, the interface says exactly that.