INTENT SOLUTIONS · OPERATING ATLAS · 01 / 08 · The connected company

One company. Several ways to create value.

Intent Solutions connects applied AI engineering, reusable software, research, education, products and media around one purpose: making useful technology work reliably inside real operations.

Company architecture

BUILD CAPABILITY
COMPOUND THE WORK
One company. Several ways to create value. — relationshipsSix company functions surround a shared Intent Solutions practice. The mission guides the practice. An emerging international engineering and commercial network would coordinate opportunities and delivery. A shared operating spine supports every function. sets direction deliver reuse teach productize test explain coordinatesets direction deliver reuse teach productize test explain coordinate

01 / DELIVERY

Client engineering

Frame an outcome; engineer workflows, integrations, agents and human controls.

  • Architecture → deployment → operation

03 / KNOWLEDGE TRANSFER

Education & community

Practice engineering judgment through shared methods, artifacts and review.

  • Learn · peer practice · proof paths

THE CONSISTENT MISSION

Close the deployment gap

Turn changing AI capability into reliable, measurable work people can own and improve.

ONE APPLIED AI ENGINEERING COMPANY

Intent Solutions

Frame → Build → Prove → Operate. Models and providers remain replaceable components.

  • Outcome · evidence · accountable owner

EMERGING SEVENTH ARM

Engineering network

Connect customers, originators and independent specialists through accountable coordination.

  • Terms and capacity still being established
Proposed model

Shared operating spine: source and decisions · durable work tracking · governed knowledge · release evidence · production operations.

The estate is the work, knowledge, tools and relationships that reinforce the company. Its websites are entry points into that system.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint.html

INTENT SOLUTIONS · OPERATING ATLAS · 02 / 08 · How the work compounds

How one piece of work can compound.

Engineering creates more than a finished implementation. With clear permissions, evidence and ownership, it can also create reusable assets, teaching material and new questions worth solving.

CREATE AND PROVE
CHOOSE WHAT MAY TRAVEL
LISTEN, QUALIFY AND REUSE
How one piece of work can compound. — relationshipsA real workflow problem moves through engineering and evidence to a rights and reuse decision. Work may remain private or become tools, knowledge or products. Use and audience feedback can create qualified conversations and better briefs that restart the loop. This is an intended operating model, not a proven revenue engine. scope test assess failed → revise retain publish teach productize private to brief adoption knowledge to discovery products to feedback qualify reframe use · failures · new needs brief to problemscope test assess failed → revise retain publish teach productize adoption qualify reframe use · failures · new needs

INPUT

Real workflow

A problem, its constraints, an intended outcome and a way to judge success.

WORK

Engineering

Integrate, build, handle exceptions and establish operating ownership.

CHECK THE CLAIM

Evidence

Test the behavior, record limits and use failures to change the work.

DELIBERATE DECISION

Rights & reuse

Choose what stays private and what can be released, taught or productized.

KEEP PRIVATE

Retained capability

Client-specific knowledge, protected IP and operating documentation.

PUBLISH WHERE APPROPRIATE

Reusable tools

Skills, plugins, integrations and source others can inspect and adapt.

EXPLAIN AND TEACH

Shared knowledge

Demos, lessons, field notes and research with their evidence and limits.

OWN THE REPEATED PROBLEM

Focused products

A maintained product when a repeated need supports a distinct offering.

RETURN TO THE WORK

A sharper brief

Reuse lessons and test the next problem.

HUMAN COMMERCIAL WORK

Qualified relationship

Establish fit, authority and a real need.

AUDIENCE RESPONSE

Discovery & trust

People inspect, learn, adopt and ask.

PRODUCT FEEDBACK

Use & operations

Observe friction, failures and new needs.

A failed test sends the work back for correction before it can support a wider claim.

Compounding requires deliberate choices at each handoff. Attention, adoption, qualified demand and revenue are different outcomes.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-compounding.html

INTENT SOLUTIONS · OPERATING ATLAS · 03 / 08 · The delivery system

From an outcome to an owned operation

Frame → Build → Prove → Operate is the shared method. Each handoff carries a concrete artifact, an acceptance condition, and a responsible person.

SHARED METHOD · APPLY TO THE ACTUAL ENGAGEMENT
HANDOFF ARTIFACTS · DEFINE OWNER AND ACCEPTANCE
From an outcome to an owned operation — relationshipsFour delivery stages connect left to right. Each produces an artifact below. A failed release decision sends work back to the build; operational findings return to the scope and baseline. This is the delivery method, not a record of universal implementation. scope test accept produces produces produces produces Failure → correction → rerun Operating evidence → changed baseline, scope, or next problemscope test accept produces produces produces produces Failure → correction → rerun Operating evidence → changed baseline, scope, or next problem

01 / FRAME

Agree what must change

Observe the workflow with the people who own it. Define the useful result, constraints, baseline, and human decisions.

  • Business outcome → acceptance criteria

02 / BUILD

Engineer the whole workflow

Connect data, systems, models, and tools. Build exception paths and controls alongside the useful behavior.

  • Model choice follows the work

03 / PROVE

Test the claim in context

Evaluate representative work and failure cases. Review the result against the agreed standard, including its limits.

  • A demo is one piece of evidence

04 / OPERATE

Transfer, run, and improve

Establish monitoring, rollback, response, and ownership. Transfer the access and knowledge the customer needs.

  • A capable customer is an outcome

ARTIFACT

Outcome brief

Scope, baseline, success test, decision rights, data boundaries, and the intended handoff.

ARTIFACT

Versioned candidate

Source, configuration, integration contracts, operating assumptions, and testable behavior.

DECISION GATE

Evidence + release decision

Results, failures, acceptance, and authorization to release. Unmet conditions return to engineering.

ARTIFACT

Operating handoff

Runbook, access, owner, rollback, incident path, knowledge transfer, and review cadence.

The customer receives a working capability and the means to evolve it. A deployment is incomplete while operating ownership is unresolved.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-delivery.html

INTENT SOLUTIONS · OPERATING ATLAS · 04 / 08 · The operating spine

The operating spine underneath the estate.

People and agents need to know what is authoritative, what work is ready, what has been learned and what is safe to release. Separate systems hold those responsibilities; shared interfaces make them usable together.

DURABLE AUTHORITIES / EACH HAS A DISTINCT JOB
INTERFACES AND BOUNDED ACTION
RELEASE, OPERATE AND LEARN
The operating spine underneath the estate. — relationshipsThree durable authorities hold source and decisions, Beads work state and governed knowledge. Skills, MCP tools and agent sessions use those authorities to perform bounded work. Review and release gates connect work to deployment, operation and new evidence. Arrows show responsibility and information flow, not a claim that every integration is fully automated. procedures claim work cited recall shared method tools evidence authorized release run observations propose lessonprocedures claim work cited recall shared method tools evidence authorized release run observations propose lesson

INTENT OS + REPOSITORIES

Source & decisions

Source code, company policies, interface contracts, operating docs and recorded decisions.

  • Git history · explicit authority

BEADS + DOLT

Durable work

Issues, dependencies, claims, acceptance evidence and task history across sessions.

  • Dolt database authority · Git code history

BOB’S BIG BRAIN

Governed knowledge

Capture proposals, apply governance, retrieve cited knowledge and verify audit receipts.

  • Compile → govern → retrieve

REPEATABLE PROCEDURES

Skills

Specify the method, required context and completion conditions for a class of work.

ACCESS TO CAPABILITIES

MCP & tool interfaces

Expose bounded tools and retrieval. Access still follows the tool’s permissions.

EXECUTION AND JUDGMENT

People & agent sessions

Recover context, claim work, act within scope and leave evidence for the next session.

DECIDE WHETHER TO SHIP

Review & release gates

Check acceptance, tests, changes and required human decisions before release.

A CONTROLLED CHANGE

Deployment

Versioned release, verification and an available rollback path.

AN ACCOUNTABLE OWNER

Operation

Observe health, respond to failures and maintain recovery procedures.

CLOSE THE CONTEXT LOOP

Evidence & proposals

Record what changed. Propose useful lessons for governed recall.

The model can change without losing the company’s source, work history or governed knowledge. Durable state belongs to systems with explicit owners and rules.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-spine.html

INTENT SOLUTIONS · OPERATING ATLAS · 05 / 08 · How a claim becomes evidence

From a claim to a release decision.

A useful evaluation names the task, criteria, scope and result. The Intent Eval Platform separates methodology, executable checks, shared evidence contracts and rollout decisions so the conclusion can be inspected.

DEFINE
EXECUTE AND MEASURE
PRESERVE EVIDENCE
APPLY POLICY AND RECORD THE DECISION
From a claim to a release decision. — relationshipsThe six-repository Intent Eval Platform connects Lab methodology and Core contracts to task cases, deterministic checks and behavioral evaluation. Checks emit an Evidence Bundle; the rollout gate combines it with a policy and emits a decision record for the dashboard. Failure returns to the test or implementation. This shows the architecture, not universal deployment coverage. method contracts to cases criteria cases checks results schema evidence policy decision signed result failed → revisemethod criteria cases checks results schema evidence policy decision signed result failed → revise

METHODOLOGY

Intent Eval Lab

Define the question, test method, failure cases and interpretation limits.

SHARED CONTRACTS

Intent Eval Core

Versioned types, schemas, validators and state definitions make results comparable.

SCOPE THE CLAIM

Task cases & criteria

Choose representative work, expected behavior and cases that must fail.

DETERMINISTIC CHECKS

Audit Harness

Check declared source and test-policy requirements with reproducible gates.

BEHAVIORAL EVALUATION

J-Rig

Exercise an artifact against explicit criteria; preserve observations and judgments.

SHARED RESULT ENVELOPE

Evidence Bundle

Carry the result, scope and supporting evidence in the platform’s versioned contract.

  • Inspectable evidence · declared limits

DECLARED DECISION RULE

Rollout policy

State which results permit this release and which conditions must block it.

Published results are scoped observations, not blanket certification.

Labs investigates and explains. Evals defines result meanings. Harnesses perform checks. A rollout policy decides whether a specific result permits a release.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-evidence.html

INTENT SOLUTIONS · OPERATING ATLAS · 06 / 08 · People, practice & authority

People, practice and permission to deliver

People can learn, contribute, introduce opportunities or deliver specialist work. Each responsibility needs its own evidence and authority.

01 / PRACTICE ENTRY · CURRENT ONBOARDING CAPABILITY
02 / CUSTOMER RESPONSIBILITY · PROPOSED QUALIFICATION AND AUTHORIZATION
People, practice and permission to deliver — relationshipsCurrent practice entry requires human review and verified agreements. The reviewer may request clarification, pause or decline. Proposed customer-work qualification checks role evidence and current fit separately; insufficient evidence returns for reassessment, while unavailable capacity pauses assignment. Practice access never grants customer-delivery authority. review approve verified review to review-alternative review-alternative to review engineering-proof to capability commercial-proof to capability supported fit capability to reassessment reassessment to capability capacity to no-fitreview approve verified supported fit

An introduction

Request access

Share relevant work, your contribution and why the practice fits.

  • Public or sanitized private work
  • Purpose and permission to continue

A bounded decision

Human review

Resolve material gaps and decide whether to continue the introduction.

  • AI can organize evidence
  • A person retains the decision

Documented relationship

Onboarding agreements

Complete the applicable NDA and User Agreement before access release.

  • Verify actual completion
  • Retain the agreement evidence

Access and welcome

Join the practice

Receive the welcome, resources and approved account access.

  • Shared method and peers
  • Optional vendor proof paths

Clarify, pause or decline

A request can stop here. New evidence can be reviewed.

Role-specific proof

Engineering evidence

Explain the implementation, tradeoffs and failure handling.

  • Ownership · evaluation · handoff

A different contribution

Commercial evidence

Show discovery, opportunity quality or domain judgment.

  • Attribution · context · references

Role-specific judgment

Assess capability

Compare the work with the role and responsibility.

  • Claimed ≠ observed
  • Credential ≠ delivery readiness

A current commitment

Confirm engagement fit

Check capacity, scope, conflicts and willingness to accept this work.

  • Availability changes over time
  • Independent parties can decline

Scope and accountability

Authorize specific work

Agree deliverables, acceptance and the accountable lead.

  • Appropriate signed arrangement
  • Access limited to the engagement

Develop and reassess

Return with useful evidence. No capability is assumed.

No current fit

No assignment. Reconsider when circumstances change.

A human decision determines progression. A persuasive application does not bypass review.

Practice access supports learning and relationships. It does not promise work or authorize representation of Intent Solutions.

Delivery evidence informs future assessments. Recheck capacity for every engagement.

Joining the practice, earning a credential, demonstrating capability and accepting a customer engagement are different decisions.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-people.html

INTENT SOLUTIONS · OPERATING ATLAS · 07 / 08 · The proposed network

The emerging international network

The proposed seventh arm connects customers, commercial originators, independent specialists and firms around work with clear responsibility.

ONE ENGAGEMENT · SELECTED ROLES, EXPLICIT AUTHORITY, DEFINED RESPONSIBILITY
ARRANGEMENT FOLLOWS CONTRIBUTION · COMMERCIAL MODELS TO VALIDATE
The emerging international network — relationshipsCustomers, originators and delivery specialists interact through an Intent coordinating layer inside one engagement boundary. Below them are three families of possible arrangements. The model is proposed, participants may hold multiple roles, and independent business remains outside the boundary. scope evidence context alignment scope deliveryscope evidence context alignment scope delivery

Problems · constraints · outcomes

Customers

Bring the operating context and the authority to define and accept the work.

  • Business owner · success criteria

Relationships · discovery · presales

Origination

Develop qualified opportunities and clarify why the work matters.

  • Referrals and customer relationships
  • Domain context and commercial judgment
  • Contribution documented per engagement

Coordination and accountability

Intent operating layer

Assemble the engagement and make responsibilities inspectable.

  • Qualification · agreements · architecture
  • Shared tooling · review · quality assurance
  • Customer responsibility · operations
Proposed model

Engineers · specialists · firms

Execution

Bring capable people, relevant assets and an agreed delivery commitment.

  • Implementation and technical judgment
  • Independent individuals or companies
  • Scope and capacity confirmed for the work

Opportunity contribution

Referral or presales

Define the opportunity, attribution and responsibility.

Proposed model

Delivery contribution

Subcontract or joint delivery

Define parties, scope, acceptance and risk allocation.

Proposed model

Ongoing responsibility

Managed work and support

Define ownership, service boundaries and the exit path.

Proposed model

Participants may hold multiple roles. Joining the network does not assign unrelated customers, business or intellectual property to Intent.

Intent must earn its role through identifiable value. Each engagement defines who contributes, who contracts and who answers for the outcome.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-network.html

INTENT SOLUTIONS · OPERATING ATLAS · 08 / 08 · Principles & open decisions

A consistent mission. Evolving methods.

The estate needs enough consistency for people to work together and enough freedom to adapt as models, markets and operating conditions change.

ENGINEERING AND KNOWLEDGE
PEOPLE AND ADAPTATION
A consistent mission. Evolving methods. — relationshipsSix operating principles connect to one central mission. Model independence, evidence and reusable intellectual property sit on the left. Opportunity without entitlement, distributed accountability and adaptation sit on the right. The central standard survives changes in models, tools and organization. model-independent to mission prove-operate to mission compound-ip to mission opportunity to mission accountability to mission adapt to mission

01 / Implements can change

Model agnostic by design

Choose models and vendors for the work. One vendor relationship does not define the company.

  • Multiple tools · one evidence standard

02 / Delivery continues after release

Build, test, prove, operate

Pair implementation with evaluations, human controls and operating responsibility.

  • Acceptance · observability · recovery

03 / Preserve what can be reused

Compound useful IP

Turn relevant learning into reusable assets while respecting customer and contributor rights.

  • Owned assets · licensed reuse · open source

The mission holds

Reliable work in real businesses

Close the gap between AI capability and work an organization can trust, own and improve.

  • Outcome and accountability stay explicit
  • Methods evolve with evidence

04 / Participation has distinct forms

Opportunity is earned

Community, education, qualification and commercial authority are separate.

  • No automatic entitlement to paid work

05 / Keep accountability legible

Distribute capability

Work can span people, firms and countries while each engagement has clear responsibility.

  • Who decides · who delivers · who responds

06 / Learn before scaling

Stay fluid with direction

Change tools, delivery methods and experiments when evidence supports the change.

  • Stable mission · revisable implementation

These principles explain the operating vision. Specific policies and contractual commitments require their own decisions and evidence.

Keep the outcome, evidence and accountability clear. Adapt the technology, delivery structure and commercial experiments as the work teaches us.

Solid: work / artifacts · Dashed: feedback · Dotted: control / support · Dashed boundary: proposed. Review 2026-10-11. Sources and scope: https://intentsolutions.io/estate-blueprint-principles.html