Building in public
Know what you would still owe if the work stopped. Who Lucid is for, what is built, and what we need to learn.
Will the projects keep coming?
Your agreements cannot tell you whether another production partner will sign.
What would I still have to pay?
The signed terms can fix that amount. If they allow more charges, you see that too.
The terms show what Vela has committed. A possible project payment is still uncertain.
It shows what you have agreed to pay and the cost of changing those agreements.
You choose how much money to keep. A change that would leave less is refused.
If the terms leave extra charges open, you see that instead of a made-up maximum.
The work can stop while the bills keep coming.
Your bank balance may include money already owed for rent or supplies. See those payments before taking on more.
People running a business on their own money. If the business loses money, they do too.
We are starting with small studios. Vela, our fictional screen-development studio, has writing agreements, rights options and office bills that need reading before it commits more.
A small studio has a limited set of agreements: rent, people, software and project work. Those written terms give us something concrete to test.
Vela is an invented example. Its story is not evidence from a customer.
In development.
The code that adds up recorded payments is written and tested. The full decision process and supporting connections are still being built.
A spreadsheet can hold your bills and do the sums. Lucid would also check each change against the money you chose to keep.
Your accounts and project tools still have a job. Lucid focuses on the moment you agree to spend or change a contract.
AI can help explain a result. It cannot set the numbers that decide how much you may spend.
We still need to test whether this is worth using another tool for.
You can trace each amount back to recorded facts. AI cannot set the numbers or approve spending. Questions about odds get a refusal with a reason.
Once you make and record a change, it leaves the list. There is no daily alert about the same contract.
You arrange the change. Software cannot make a supplier accept new terms.
Can people running studios check the figures, spot terms they want to change, and find the help worth paying for?
We have a written test plan, but no studio-session results yet.
We are considering a subscription. No price is set.
It could cover new decisions as bills and contracts change. Whether studios would pay for that is still untested.
Studio sessions will help us decide what to build next and whether entering terms is worth the effort.
The Vela examples cover existing bills and an optional rights agreement. Managing new opportunities remains exploratory and needs its own evidence before it becomes a product feature.
The worked example and the sums behind it are on Why Lucid.
Lucid
We keep a written record of the rules and what we build.
Puntoria
Puntoria builds Lucid.
The method
Lucid's method comes from the Incerto. We record which passages support each rule and where we have made our own decisions.