Frequently asked questions

Questions leaders ask before the first call.

Answers on scope, control, proof, data and cost. If your question isn't here, bring it to the call.

Business questions

What is Fabrica?

Fabrica is a technology renewal service in development, built by Thinslices. It uses a five-stage method called CLEAR to renew production systems by workflow or customer cohort while the current system keeps running.

What is the CLEAR method?

CLEAR stands for Capture, Lock, Engineer, Attest and Release. Capture records how the running system behaves. Lock approves and locks a version of the System Specification, and later changes go through a new version. Engineer rebuilds the scoped workflow, with engineers reviewing the changes. Attest tests the rebuild against the running system using the same specification. Release moves production over by workflow or customer cohort, with acceptance criteria and rollback.

Does every system need rebuilding?

No. Keeping a stable system, upgrading it or refactoring a narrow part may be the better investment. Fabrica's reconstruction approach is for cases where replacement is justified. Ongoing renewal aims to slow the build-up of deferred change, though it won't remove all future migration work.

What does the first conversation involve?

Thirty minutes on one business priority, the system behind it and the constraints on changing it. We identify a useful first scope and what a technical review would need to establish. No production access is needed.

Who stays in control?

A business leader, usually from the executive team or finance, sponsors the work. Your engineering lead works with us on scope, evidence and acceptance, and your technical team decides when each workflow moves.

What does ongoing renewal mean?

The proposed model starts with an assessment and a bounded pilot, followed by a recurring plan for agreed priorities. In each cycle we refresh the evidence and specification, deliver selected changes and verify outcomes. Scope, cadence, fees and exceptions are agreed before you commit.

Is there a free option?

Yes, documenting your live system is free. Our team documents your live legacy system at no cost, using read-only access agreed with your engineers, and you keep the documentation. In return we ask for feedback on the service.

How much does it cost?

Pricing depends on scope and is set after an assessment. The assessment fee is agreed before work starts. We are testing two models, an assessment-first route and a renewal subscription, and do not publish a list price while the service is in development.

Technical questions

Do we need a code freeze?

Not by default. Parallel builds and incremental replacement work without a whole-system freeze. If a specific scope needs one, for example during a data cutover, we agree what it covers and how long it lasts. We aim for days or weeks for an agreed scope, and a pilot measures the result.

How do you know the new version does what the old one did?

Both implementations are compared against the same specification. We replay or shadow representative workloads with side effects controlled, and check business outcomes, data integrity, reports, permissions and performance. Differences are investigated and resolved before any traffic moves.

What happens to our data and reports?

Data cutover is a separate workstream. Before live writes route to the new implementation, we define mappings, backfill and sync, write ownership, reconciliation and rollback. Important report totals are reconciled against the current system.

What access do you need, and how is sensitive data handled?

The first call needs no access. An assessment needs read-only access to code, schema and available analytics, agreed with your technical team. Sensitive payloads are redacted, collection overhead is measured and collection failures are kept off the request path.

Which technologies do you support?

We are starting with web applications built on Ruby on Rails, typically backed by PostgreSQL, Java Spring, .NET Framework, PHP and Django.

Where does the code live?

In your repository. Changes arrive as reviewed pull requests, and you choose where the code runs.

What if something goes wrong after a release?

Each release has acceptance criteria and a tested rollback. The current system keeps running until a workflow has been fully moved and verified, so rolling back means changing the routing, with no redeploy.

Which priority is your system holding up?

Tell us about it on a 30-minute call. We'll suggest a first scope and what a technical review would need to confirm.

Book a 30-minute call