Predict the future

You didn’t come this far to stop

Here is the current Cerone technical/coding stack, as it exists in the monorepo.

Core Runtime

- Python is the main implementation language.

- Monorepo layout lives in [cerone-monorepo](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo).

- Python SDK is in [sdk/python/cerone](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/sdk/python/cerone).

- Local server is in [server/cerone_server](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/server/cerone_server).

- HTTP API uses Python’s built-in `http.server`, not FastAPI or Flask right now.

- In-memory state is used for agents, trust, and audit logs. There is no database yet.

- Policy engine is Python code plus JSON policy files.

Configuration And Policy

- JSON policy files define governance behavior:

- [default_policy.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/policies/default_policy.json)

- [generic_email_policy.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/policies/generic_email_policy.json)

- [generic_admin_policy.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/policies/generic_admin_policy.json)

- [finance_policy.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/policies/finance_policy.json)

- [pharma_policy.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/policies/pharma_policy.json)

- [policy_template.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/policies/policy_template.json)

- Policy composition features:

- `extends`

- `rule_sets`

- `use_rule_sets`

- Policy validation happens at load time in [policy.py](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/server/cerone_server/policy.py:1).

CLI And Ops

- CLI entrypoint is [server/cerone_server/__main__.py](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/server/cerone_server/__main__.py:1).

- Available commands:

- `cerone serve`

- `cerone policy check <file>`

- Shell script runner exists for the customer demo:

- [run_customer_demo.sh](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/demo/run_customer_demo.sh)

- Yes, this is the `.sh` file you mentioned: it starts the local server and runs the demo flow.

Packaging

- `pyproject.toml` is used for packaging and tool config:

- [pyproject.toml](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/pyproject.toml:1)

- Editable install works with `pip install -e .`

- Console scripts are defined in packaging:

- `cerone`

- `cerone-local`

Demo / Presentation Layer

- Customer demo Python script:

- [customer_demo.py](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/demo/customer_demo.py)

- HTML widget/report is generated as a static file:

- [customer_demo_report.html](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/demo/customer_demo_report.html)

- JSON demo artifact is also generated:

- [customer_demo_results.json](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/demo/customer_demo_results.json)

So the current “customer-facing widget” is plain generated HTML, not React or a web app.

Testing

- Pytest is the testing framework.

- Test coverage includes:

- SDK behavior

- engine behavior

- policy loading and composition

- CLI behavior

- customer demo artifact generation

- Tests are in [tests](/Users/Anant/Desktop/all%20files/Ceron_SDK_/cerone-monorepo/tests).

Docs / Repo Materials

- README

- architecture docs

- policy authoring docs

- release strategy docs

- demo docs

- contributing guide

- Apache-2.0 license

Not In The Stack Yet

- no database

- no web dashboard app

- no Docker setup yet

- no n8n integration yet

- no Azure integration yet

- no .NET / Go / Rust SDKs yet

- no premium control plane yet

So the short version is:

- Python for SDK, server, CLI, demo logic, and tests

- JSON for policy definitions

- Shell (`.sh`) for demo orchestration

- HTML for the generated demo widget/report

- Pytest for validation

- `pyproject.toml` for packaging and CLI entrypoints

If you want, I can turn this into a proper `TECHNICAL OVERVIEW.md` file in the repo.