Charter | Customer-Operated Company System

Choose the audience that matches your question

The page contains three selectable readings of the same subject.

Coding agent and operator assistance. Demo metrics are illustrative.

Terminal, search, lint, test, git, and more.

Remembers your codebase and team context.

Specialised agents collaborate across concerns.

Review diffs, request changes, final sign-off.

Replay any session bit-for-bit when something needs review.

Autonomous agents that write code and keep receipts

to handle network timeouts, 5xx responses, and idempotent-safe conditions. Pure helper, fully unit-tested.

included in eligible licensed Dweve platform scopes

source and modification rights selected explicitly

vendor change, infrastructure change, policy change, and model change each trigger migration

the same source tree and operating graph continue across every event

a Germany pack overrides XRechnung and selected VAT behaviour

the rest inherits the shared EU baseline

source continuity is the shared rail beneath all postures

party spine, money spine, work spine, knowledge spine, event spine

from permanent company state to temporary AI work

Charter occupies the durable company layer

Loom provides the cognition Charter can call

Spindle preserves knowledge, Mesh supplies capacity

Core and Kera provide the computational foundation

Charter is the included operating ground beneath them

the Charter line is part of the licensed platform; source rights remain an explicit commercial choice

answers drawn from the domain-specialist catalogue

the customer identity rail stays visible beneath every stage

a legal-basis and dependency check chooses the outcome

derived copies fan out beneath each source and are included in the sweep

the domain shapes match while the data and policy boundaries stay separate

live since day one, running Dweve itself

every connector enters the same policy boundary and none owns the company context

native lanes, deepest trace and provenance

in the fragmented state each right is attached to a different vendor

in the Charter state all eight return to one customer-owned boundary

each lens reveals a different context over the same underlying identity

the doors between rooms are API bridges employees carry folders across

the same customer appears with a different badge in every room

the AI participant enters through a company gate

sensitive rooms stay closed and the company graph stays outside the model boundary

hands over CSV files while schema, rules, workflows, and source stay locked behind the vendor

a separately contracted right can cover the operating layers named in the agreement

the proposal is bound to the user, expires, and states what will change

only what the current user may already see

bound to the user, expiring, and explicit about the change

reviews exactly what will change before it commits

current permission and record re-checked at commit

applied once, in a single all-or-nothing step

a signed record of who approved what, and when

one action flows through quote, invoice, project, and support

the old path shows copy and paste at every handover

the person does not carry the story by hand

one company story across everyday operations

the AI helper works from real, permitted records

Charter included in eligible platform scopes

source rights remain a separate contract choice

connected, private-site, and offline licensed estates

one customer thread moves through every room without being copied

a key and a source document sit with the owner

the place that runs it belongs to you too

the same Charter system, kept in a different place

a line of copies (file, AI memory, and search) follows the same decision

different helper icons enter the same company home through one permissions door

Charter is visibly included beneath them

no separate Charter bill appears anywhere

the same customer stays visible through the whole journey

the owner is shown correcting each card by hand

shared records move between the rooms instead of being retyped

the helper is given only the related records it may see

the answer points back to the records it used

on one side the subscription switches off and the app disappears, leaving CSV files

on the Charter side your system and your work keep running

both are built from the same Charter blueprint

no product is drawn as a renamed layer of another

per-class erasure including derived data

graph, policy, workflows, and licensed runtime

each mechanism displays one hard invariant it will not break

the Article 17 sweep follows every edge and applies a per-class action

statutory finance and executed signatures retain their legal basis

masked fields remain visibly present but inaccessible without purpose

one user action and one API action traverse the same policy and graph contracts

a source tree and deployment boundary visibly enclose the graph

the money-moving path is idempotent and forward-only

the financial history stays in the graph

the Dweve path carries additional typed evidence lanes

the general provider path carries the standard response and capability record

both remain governed by the same action boundary

the domain transaction commits state and outbox record together

the Germany pack overrides XRechnung and VAT

the remaining capabilities inherit the EU baseline

a merge repoints edges and leaves a tombstone and audit row

untrusted tool output returns inside a nonce fence

the write path terminates at a proposal object, not the database

HMAC verification, user binding, expiry check, policy recheck, state recheck, commit, event

each model advertises different capabilities into one invocation contract

company context stays on the Charter side

becomes a real project task idempotently

and a notification, retaining party, project, and audit links

idempotent, no duplicate task on redelivery

the write node visibly creates the pause for confirmation

storage, cache, queue, database, and realtime adapters change; the domain and policy code do not

the core does not change between profiles

when operational source rights are contracted, the named repository maps to the licensed runtime

a dense translation mesh reconciles seven incompatible semantics

Charter replaces the mesh with shared contracts

the same graph runs from UI, API, schedule, event, or AI proposal

A few invoices are still open. Want me to send a friendly reminder?

The deed is the responsibility line for the company: what is owned, what is governed, and what remains auditable. It gives every later section a clear place to return to.

Every domain engine reads and writes the same typed graph. Records, policy decisions, and event history stay linked instead of being translated between vendor systems.

A company home is useful when the story stays connected. You can open the customer, invoice, project, or document and see the context without remembering which app owns the next piece.

A normal business runs on a pile of separate apps. One for customers, one for invoices, one for projects, one for staff, one for chat. They do not really talk to each other, so the same information gets typed in again and again. Charter is different. Customers, money, projects, people, support and your company knowledge all live in the same place, so you only ever keep one copy of the truth.

You do not have to be technical to use it. If you can read a page and click a button, you can run your company from here.

Here is the part that makes Charter feel different. Imagine someone fills in a form on your website. In most companies that person then gets copied from app to app, and bits get lost along the way. In Charter they stay one record the whole way through. They become a customer, get a price, sign, pay, you do the work, and later you help them again. Same record, start to finish, never typed in twice.

Charter comes with a helper that can save you time. It can write a friendly reply, draft a note, or get a task ready for you. The important part is how polite it is. It never changes anything on its own. It shows you what it wants to do, in plain words, and waits. Nothing happens until you press yes. Your records stay yours, and you are always the one in charge.

Stop juggling a dozen apps that do not talk to each other. Keep your customers, your money, your work and your team together in one place you own, with a helper that always asks before it acts.

Charter is business software that keeps customers, invoices, projects, support, documents, and notes together. In most companies they live in separate apps, so one change becomes six updates and one customer becomes six different records.

The built in helper works from the records you can see, shows what it proposes, and waits for your approval before anything changes.

Most companies legally own the business while vendors own its operating fragments. Charter brings customers, money, people, delivery, support, knowledge, and AI actions onto one operating graph within an eligible licensed Dweve deployment. The licence covers operation; source code and modification rights are separate choices.

One company record from first signal to renewal. One policy path for people and AI. No separate Charter charge.

Charter is a single company operating system. Instead of buying a separate tool for sales, another for invoicing, another for HR, another for support and wiring them together later, you run all of it in one place. Customers, money, projects, people, support, knowledge and documents share the same records, the same login and the same audit trail. Nothing is copied between apps, because there is only one system.