Software shouldrevolvearound you.
Kraton brings reusable functions into software you control. Keep your data and rules. Add capabilities as your needs change.
Service-centeredPerson-centered
You hand your work to services. They keep your data, and your trust.
Animated comparison of service-centered and person-centered software. At first, a person sits outside three services that hold their bookings, invoices and transactions, and two of those services rebuild the same money logic. Then the person moves to the center: their information comes back to one place, and checked functions gather around them, each one reused instead of rebuilt.
Hover a function to read its contract.
Start witha real result.
Pick a job and see what comes back: a budget, a checked invoice, a booking page, a narrow assistant action. Each one states what runs today and what is still open.
See use casesNew need.Same software.
Add a function. Adjust a rule. Keep the application and state you already use.
INTERFACE
RULES
DATA
214 invoices
38 vendors
on your Mac
Interface, rules and data. The part that makes it your app.
Invoice check
invoice-validator 0.2.1
Runs todayExact money
exact-money 0.1.0
KR-002 openreusablePayment file
payment-file host
ConceptBudgets, invoices and expense reports can build on the same money arithmetic, each with its own rules and data. Nobody shares your app or your data.
Runs on your Mac Kraton Engine
- Uses the invoices it is given
- Writes the payment file after your OK
- No network
Illustrative app. Invoice check runs in current demos, exact money has an open order, the payment file and duplicate check are concepts.
Different apps.The same hard problems.
Reuse a function whose contract fits. Spend your time on the rules and experience that make your software yours.
Explore reusable functionsThree lists that sync, each rebuilding the sync. You pay for every copy.
Sync and mergesync v7
their copy · evidence not public
Sync and mergecustom
their copy · evidence not public
Sync and mergev2.3
their copy · evidence not public
An illustration of the model. Service, app, and component names are generic examples.
See what has been checked.And what still needs proof.
Each record names its contract, its version, and the evidence behind a specific property. Choose the depth of verification your use requires.
booking-conflictIllustrative record
Decides whether a requested booking can be accepted.sha256:3b7e…a91cVERSIONS
Today Candidate logic from the booking demo. The contract is still a set of examples.
PROPERTY
An accepted booking must not overlap a conflicting event, under the stated calendar and time-zone assumptions.
CONTRACT
Examples only. Three calendar fixtures show the intended behavior.
Exact types, time zones, and boundaries are part of the open order.
PERMISSIONS
- Uses the events it is given
- No calendar access
- No network
- No clock
EVIDENCE FOR 0.1.0
deeper ↓- 01Example fixturesRuns against local calendar fixtures
Attached
maintainer · demo suite - 02Versioned contractTypes, time-zone rules, interval boundaries
Open · KR-001
Fund this check - 03Adversarial casesSimultaneous requests, DST, rescheduling, write failures
Open · KR-001
Fund this check - 04Independent reviewCandidate logic checked against the contract
Open · KR-001
Fund this check - 05Machine-checked proofNamed pure property: no overlap
Optional bid
if a bid is accepted
Confidence is earned.Together.
Bring a need. Fund a precise contract, independent checks, or a proof of the property that matters. Compatible requests can support one reusable result.
OPEN BOARD · 3 orders, as published
Real orders, shown as they stand.
01Request
A need is posted with the property to establish.
KR-001Scope open
Specify and verify booking conflict rules
No committed budget0 public offersDue 12 October
KR-002Scope open
Specify the budget CSV calculation contract
No committed budget0 public offersDue 12 October
KR-003Scope open
Specify a public Beacon handoff pilot
No committed budget0 public offersDue 12 October
02Specify
Specialists make the requirement exact.
Versioned contract
No order here yet03Offers
Verifiers quote a method, scope, and price.
Screened public quotes
No order here yet04Evidence
Cases, a review, or a proof is delivered.
Report or proof, tied to a version
No order here yet05Reusable
The evidence ships with a version.
A version anyone can pin
No order here yetHow one guarantee travels
How it is designed to workYou
Your booking app needs one guarantee: no double bookings.
Other owners
People who need the same property back the same order.
Verifier
An independent verifier quotes a method, then delivers.
Registry
The evidence attaches to one exact version.
Everyone
Every app that pins that version inherits the evidence.
Early orders are coordinated manually. Reuse rights are agreed before work begins.
Offer a methodShort
answers.
What can I use today?
Companion and the supported local demos. Each use case shows its current path and status.
Is this just another app generator?
You can choose how the interface and candidate code are created. Kraton focuses on reusable functions, their evidence, and controlled execution in software you keep using.
Is every component mathematically proven?
No. Each record states its actual checks. You can request independent verification or fund a formal proof of a named property.
What do I pay for?
Agreed work on specifications, verification, proofs, missing implementation, or optional support. Basic local use and published common logic are free.
Do I need Beacon?
No. Choose the contact channel that fits your use.
Does local mean no cloud receives data?
The Kraton execution boundary is local for local workflows. Your AI provider and chosen integrations may process data you send them.
Bring the center
back to you.
Start with the local app. Reuse common functions. Put missing specifications and verification on the open market.