PRODUCT DIRECTION
Deedseal Platform
The owner-governed core: worker roles, permission grants, run records and business memory.
Pre-release / design-partner stage
For business owners and operators
Deedseal is an owner-governed AI business platform for deploying and operating a business.
Deploy your business. Keep the last word.
Deploy an AI office for your business while keeping authority, business memory and the final decision with the owner.
Bounded AI workers are designed to run your routine workflows across the tools you already use.
Pre-release / design-partner stage. Not generally available or production-qualified.
What you receive
Four things, and no hidden fifth.
A design-partner engagement is scoped around four deliverables. Nothing else is implied, and no price is published.
PRODUCT DIRECTION
Configurable Modules
Operating modules selected and configured for your business. Configuration and bounded adapters, never a client-specific fork of the core.
PRODUCT DIRECTION
Deployment
The configured platform placed on the owner-controlled boundary agreed during the pilot.
PRODUCT DIRECTION
Care and updates
Continuing support, platform updates and new worker-role templates as the business changes.
PRODUCT DIRECTION
Separately accounted model usage
External model usage is intended to be accounted for and passed through separately from service fees.
No price is published. Scope and commercial terms are agreed per design-partner engagement.
Connect what you already use
The systems your business already runs on.
Deedseal is designed to work around your existing tools rather than replace them. Each connection below carries its real maturity.
Every capability carries its real maturity.
- PUBLISHED PROOFYou can check this today against the pinned public record.
- IN DEVELOPMENTWork is under way in a public repository. It is not finished and not proven.
- PRODUCT DIRECTIONIntended product scope. Nothing is built, connected or proven yet.
A label is never raised without evidence a reader can open.
PRODUCT DIRECTION
Documents and storage
Open, file and extract from business documents under a grant that names what may be read and what may be written.
Shared drives, document stores and the business's own file systems.
PRODUCT DIRECTION
Email and calendar
Triage, draft and schedule. Anything that leaves the business waits for a person to accept it.
Business mail and calendar services such as Google Workspace and comparable suites.
PRODUCT DIRECTION
Communication and social
Prepare internal summaries and outbound drafts, held for review before anything is published.
Team messaging and public business profiles such as LinkedIn, Facebook and X.
PRODUCT DIRECTION
Sales and CRM
Capture and route enquiries, keep records current, and prepare the follow-up a person then approves.
Lead inboxes, pipelines and customer-record systems.
PRODUCT DIRECTION
GitHub work plane
GitHub remains authoritative for its Issues, pull requests, reviews and checks. Deedseal is designed to read the current object, route bounded work, wait for Owner acceptance and return named checks backed only by accepted evidence. No live Deedseal Check Run or GitHub partnership is claimed here.
Issues, pull requests, reviews and named checks.
IN DEVELOPMENT
Model-provider boundary
The public record carries a broker boundary between the platform and any model provider. One provider is pinned in that record; portability across providers is not proven.
A broker contract that keeps provider and model separate from the work itself.
PRODUCT DIRECTION
Named model providers
No named provider connection is publicly evidenced today. Where one is configured, external model APIs may receive policy-authorized request payloads.
Third-party model APIs the broker is intended to address, such as OpenAI, Anthropic and Gemini.
IN DEVELOPMENT
Vertical adapters
The construction/ADU module is being built in the open as the Owner-operated reference configuration.
Industry operating modules, beginning with construction and ADU work.
No vendor logo, badge or partner mark is shown anywhere on this page. Naming a system describes intended scope only; it does not indicate a relationship with, or endorsement by, that vendor.
How it operates · product direction
Five steps, and you hold the fourth.
One loop runs behind every workflow, so what a worker may do is legible before it does it.
- 01
Connect context and tools
Business documents, records and systems are brought into reach under an explicit, named grant.
- 02
Define roles and boundaries
Each AI worker is given a role, a permission boundary and the exact systems it may touch.
- 03
Execute routine workflows
Bounded, repeatable work runs without asking for attention it does not need.
- 04
Require human acceptance
Consequential work stops and waits for a named person to accept or refuse it.
PRODUCT DIRECTION
Deterministic acceptance
Deterministic acceptance criteria are written as checks that can be rerun as code; model review remains a separate judgment.
- 05
Compile accepted work into memory
Only accepted work becomes durable business memory. Memory carries its provenance and grants no authority of its own.
PRODUCT DIRECTION
Durable-record business memory
Work state is designed to persist in durable records with exact coordinates rather than depending on a chat window.
PRODUCT DIRECTION
Closed-loop record
Only accepted work is designed to enter the owner's durable PostgreSQL record. Graph Memory is a rebuildable projection of that record, not a second source of truth.
Less scattered context
Business context stops living only in individual inboxes and individual heads.
Repeatable operations
Routine work runs the same way each time, under the same stated boundary.
Transparent handoffs
Every consequential step records who accepted it and what it was allowed to do.
Retained institutional knowledge
What the business has decided stays with the business, with its provenance attached.
These are the intended effects of the operating model. No savings, performance, productivity or time-to-value figure is claimed, measured or implied.
Workflow catalogue
The work a Deedseal office is designed to carry.
Each entry is a bounded workflow, not an autonomous department.
PRODUCT DIRECTION
Documents and records
Filing, retrieval, extraction and keeping a business record set current.
Delivered as: Configuration
PRODUCT DIRECTION
Email and calendar
Triage, drafting, scheduling and follow-up preparation.
Delivered as: Configuration
PRODUCT DIRECTION
Communications
Internal summaries and outbound drafts prepared for a person to review.
Delivered as: Configuration
PRODUCT DIRECTION
Lead and sales coordination
Capture, qualification support, record-keeping and hand-off preparation.
Delivered as: Configuration
PRODUCT DIRECTION
Research and decision preparation
Gathering sourced material and preparing an options brief for a human decision.
Delivered as: Configuration
IN DEVELOPMENT
Vertical operating modules
Industry modules; the construction and ADU set is being built in the open.
Delivered as: Configuration
Every entry is delivered as configuration and bounded adapters on one shared platform. None of them is a client-specific fork of the core.
How delivery works · product direction
From a scoped pilot to an operated system.
- 01
Scoped pilot
Agree one bounded slice of the business, the systems in reach, and what acceptance means.
PRODUCT DIRECTION
Bounded task scope
Each task begins with a declared outcome and an explicit boundary naming the systems, records and effects it may touch.
- 02
Configuration and adapters
Select modules and bounded adapters without forking the core.
- 03
Owner-controlled deployment
Place the configured platform on the owner-controlled hardware and boundary agreed in the pilot.
- 04
Care and new role templates
Recurring support, updates and new worker-role templates as the operating model changes.
External model usage is arranged and billed separately and transparently. Where a third-party model provider is configured, policy-authorized request payloads leave the boundary to reach it.
Durable business records, evidence and business memory are designed to remain on owner-controlled hardware. This is not a claim of zero egress, fully offline operation or on-premise inference.
No price or rate is published here.
First reference use · Owner direction
West Coast KBP ADU
Construction/ADU is the Owner-operated first design and reference use for Deedseal.
The full ADU cycle — land and feasibility, project operations, and the project memory that outlives them — is the worked example of how a vertical configuration is shaped. It is operated by the Owner and is not a third-party engagement.
Evidence limit: this is not evidence of a customer, deployment, outcome, adoption, partnership or accepted integration.
Trust and public proof
Permission before the work, evidence after it.
The browser-local verifier checks a published run passport against pinned evidence bytes without uploading the passport.
PUBLISHED PROOF
Signed permission grant
Before a worker takes a meaningful action, the authority it was granted is recorded and signed.
Open the pinned record (opens in a new tab)PUBLISHED PROOF
Signed run record
After execution, a run record binds granted authority, custody, identity, digests, boundary and closure, and can be checked offline.
Open the pinned record (opens in a new tab)PRODUCT DIRECTION
Durable business memory
Accepted work compiles into business memory that carries its own provenance and grants no authority.
Change one byte and the published demonstration changes from PASS to BLOCK; restore it and PASS returns.
PASS is bounded to one run’s integrity, signatures, permissions, boundaries and provenance. It is not a business conclusion, certification or proof of semantic correctness.
Only the two records above are published proof you can check today. Everything on this page labelled IN DEVELOPMENT or PRODUCT DIRECTION is not proof and is not offered as proof.
Read the pinned verification record (opens in a new tab)RECORD NOT CHECKED
Verdict produced by the vendored browser-local verifier.
No verdict yet. The verifier has not been asked to check the published passport in this browser.
PASS is evidence about this published run passport only.
- It is not approval, certification or a business outcome.
- It does not prove semantic correctness or that the workload was sandboxed.
- The passport remains in this browser; no upload is required.
Pre-release
Deedseal is at the design-partner stage.
If you operate a business and want to shape how an owner-governed AI office works, start a conversation.
Inbound delivery to this address has been verified. If a message does not reach us, the public repository route below remains open.
Technical evaluators can read the source, the verifier and the published run records at the pinned public record.
Pre-release / design-partner stage. Not generally available or production-qualified.