LASDK | Give AI the Work. Know What Finished.

Q: Will LASDK work with my AI provider?

See what has been tested . In the closed beta, Claude Code and Codex are the supported coding tools; other tools are not part of the test. You pay your provider directly, and an external provider may receive project context according to its tool, settings, and policies.

Why LASDK exists

Building the code was never the only problem.

Good products lose time when runway runs short, developers are pulled elsewhere, priorities move, or teams are interrupted.

AI changed how much one person can build. But it created another job: managing the delivery around the AI that builds it.

AI already builds.
LASDK was built for the job around it.

One delivery, end to end

“Add an approval workflow to vendor onboarding.”

You tell your AI assistant what the product needs. The assistant uses LASDK to carry the configured delivery forward, check the result, and report what finished or still needs attention.

YOU → AI“Add an approval workflow to vendor onboarding.”

AI + LASDK · DELIVERY IN PROGRESS

Understand flowImplementTest & reviewDocument

AI REPORTS BACKApproval flow implemented
Configured checks recorded
Ready for your review

WORKINGDelivery is moving.

NEEDS YOUA person responsible for the work must decide.

BLOCKEDA tool, provider, or dependency prevents progress.

DONERequired work and checks are recorded; review the result.

Illustrative example, not a live run. Steps and checks depend on the configured delivery and supported tools; a recorded DONE does not guarantee correctness.

LASDK has been used on live software work, including its own development.

Why LASDK exists

Your AI is the operator.
LASDK is the delivery system.

It doesn’t take “I’m done” on faith.

On supported paths, LASDK can require checks and record results against the delivered software. That gives you something concrete to review beyond the model’s claim.

It fits the way your team works.

Solo builders can keep delivery simple. Teams can configure responsibilities, repositories, project systems, rules, and documentation practices where supported.

The work survives the agent.

Delivery history and checkpoints live outside the model conversation, so supported work can be resumed after a session ends or a provider fails.

Your AI stays replaceable.

Use supported coding tools you choose. LASDK is the delivery process around them; it is not another model you have to adopt.

Use what the work needs

Start simple. Add structure when it helps.

One person can start simply; teams can add the practices and connections that their supported setup allows.

Solo builder

Request → Build → Check → Done

Team

Product → Engineering → Independent Review → QA → Documentation → Delivery

Why delegate delivery

The outcome is the product.

LASDK aims to help you hand over more software work without increasing human supervision at the same rate.

More work handed over

Delegate meaningful pieces of delivery, not only small interactive coding tasks.

Less babysitting

Spend less time repeatedly asking what happened and repairing broken handoffs.

A meaningful Done

Completion can be supported by the work, configured checks, review, and recorded evidence.

A useful tool is not always another tool

Sometimes your coding assistant is enough.

For a one-line change, a throwaway script, a quick prototype, or help understanding code, go straight to your usual assistant. LASDK becomes useful when work is multi-step, long-running, handed off, or hard to review by hand.

See it run

One real run, with its result and its limits.

A short recording of LASDK delivering one change, shown as it happened. Whatever was done to the recording is stated next to it, and so is what it does not show.

The demo recording is coming. When it is here it will show one real run as it happened, with the result as reported and its limits next to it.

What has been tested

Where LASDK runs today.

Live-tested means a real run on that setup, not just a build. Everything else is said plainly as not tested yet.

Setup	Status	Detail
macOS, Apple Silicon	Live-tested	With Claude Code and with Codex. On 18 Oct 2026, on 4.11.0-beta.20 candidate builds (not yet released to testers), one command delivered the same small Node project ticket on each; both ended VERIFIED & APPLIED with 0 approvals.
macOS, Intel	Built, not live-tested	A build exists. No real run has been done on it.
Linux, x64 and arm64	Built, not live-tested	A build exists. No real run has been done on it, and Linux has no OS sandbox of its own, so some protections are weaker there.
Windows	Not supported natively	Use WSL Ubuntu with the Linux build. That path was not re-tested on this build.
Claude Code, Codex	Live-tested (macOS)	The two coding tools the closed beta supports.
Other AI coding tools	Not part of the test	Some adapters exist. They have not been live-tested for delivery.
Project type	Node tested; Python not yet	The live runs so far used a Node project. A Python project failed its first live run and the fixes have not been proven yet.

Verified means the checks passed. It does not mean the code is correct. Your provider may receive project context under its own terms.

Closed beta is free, with no card required. Accepted participants receive a beta licence; the software also has a 24-hour trial, once per device. Paid plans will follow after beta. Beta participants will receive priority access to future founding plans. AI provider usage remains separate.

About

Siklab Core builds LASDK.

Siklab Core is the company and the product family. It is a small, independent software company based in the Philippines.

LASDK is its delivery engine: the part that checks, reviews and records the work an AI coding assistant does, so you can see what actually finished. It is also a standalone closed beta for developers and small teams, which is what this site is about.

Other Siklab Core products are in development and are not part of this beta. Questions: lasdk@siklabcore.com.

A few practical answers

Before you apply.

Who uses LASDK: me or my AI assistant?

You tell a supported AI coding assistant what you need. The assistant uses LASDK's tools to carry the configured delivery forward and report back. LASDK is the delivery system, not a coding model.

What does Done mean?

For a supported delivery, Done means the required work and checks were recorded for review. It does not guarantee correctness or approve a production release.

Will LASDK work with my AI provider?

See what has been tested. In the closed beta, Claude Code and Codex are the supported coding tools; other tools are not part of the test. You pay your provider directly, and an external provider may receive project context according to its tool, settings, and policies.

How does LASDK relate to Siklab Core?

Siklab Core is the company and the product family. LASDK is its delivery engine, and it is also a standalone closed beta. More about Siklab Core.

What happens when I apply?

Your application is emailed to Siklab at lasdk@siklabcore.com. The closed beta is free, with no card; if you are accepted, we send you a beta licence. You pay your AI provider separately.

Closed beta · small group

Try LASDK on real work.

We’re inviting a small number of builders and teams to use the closed beta on software they actually care about. Ask your AI assistant to carry a task you would normally supervise closely, then tell us whether the result was usable and how much you had to intervene.

Free · no card · bring your own supported AI

You pay your AI provider separately. Supported tools and access details will be shared before invitations go out.

Closed beta

Don’t judge LASDK from this website.
Give it something real.

Ask your AI assistant to take on a task you would normally supervise closely. Did it get the work done? Was the result usable? How much did you have to intervene?

Free · no card · bring your own AI

Apply for Closed Beta