Packages
arke
0.8.0
1.1.33
retired
0.8.0
0.7.0
0.6.5
0.6.4
0.6.3
0.6.2
0.6.1
0.6.0
0.5.0
0.4.5
0.4.4
0.4.3
0.4.2
0.4.1
0.4.0
0.4.0-bulk.1
0.4.0-bulk.0
0.3.17
0.3.16
0.3.15
0.3.14
0.3.13
0.3.12
0.3.11
0.3.10
0.3.9
0.3.8
0.3.7
0.3.6
0.3.5
0.3.4
0.3.3
0.3.2
0.3.1
0.3.0
0.1.38
0.1.37
0.1.36
0.1.35
0.1.34
0.1.33
0.1.32
0.1.31
0.1.30
0.1.29
0.1.28
0.1.27
0.1.26
0.1.25
0.1.24
0.1.23
0.1.22
0.1.21
0.1.20
0.1.19
0.1.18
0.1.17
0.1.16
0.1.15
0.1.14
0.1.13
0.1.12
0.1.11
0.1.10
0.1.9
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
Arke low code framework Core
Current section
Files
Jump to
Current section
Files
usage-rules.md
# Rules for working with Arke
## Understanding Arke
Arke is the core of the Arke framework: a metadata-driven, multi-tenant entity
framework for Elixir where domain models ("Arkes") are runtime data rather than
compile-time Ecto schemas. Every persisted thing — a record, a schema
definition, a field type, a group, a graph edge — is an `Arke.Core.Unit` with
the same struct shape, keyed by a project (tenant). Schemas are defined in
JSON registry files (the source of truth), while `Arke.System` modules attach
behavior hooks to them by id; loaded schemas live in ETS behind GenServer
managers, and all CRUD flows through `Arke.QueryManager`, which runs
a validation + lifecycle-hook pipeline and delegates I/O to an injected
persistence layer (usually `arke_postgres`) — core Arke performs no I/O itself.
Do not assume Ecto, ActiveRecord or JSON-schema conventions apply: read the
topic rules in `usage-rules/` before using a feature. Sibling packages plug
in: `arke_postgres` (persistence), `arke_auth` (identity), `arke_server`
(HTTP API).