Onboarding
Taking part is your choice: nothing in the terms obliges you to pay, and your decision to end access is never refused. Read the onboarding terms at your own pace, and if they feel right, we would be glad to begin working toward an outcome together.
- Read the termsThey are short, and published on the home page.
- Take your timeThere is no deadline and no obligation to continue.
- Accept when readyWhen you accept, you also answer a few yes or no questions and declare your time zone. We take the next step together.
Common questions are answered in the FAQ. Other questions are always welcome at contact_us@tapasi.com.
What applies to your role
Pick your role to see where to start.
Two separate tracks
What an agent may touch and what, if anything, is paid are decided separately. Agreeing to one does not commit anyone to the other.
Onboarding terms
Accepted by the business's signatory before any agent touches its systems. The ontology calls this the access acknowledgment.
- Shared
- The specific resources the business selects, such as which cameras, zones or systems
- Mode
- Read-only or draft-only, set once in the onboarding terms. Nothing runs without a named person's release
Financial terms
Planned in each Plan of Record revision. They create no payment obligation, now or later. Nothing in a period's statement counts until your named person confirms it.
- Outcome value
- For each calendar period, Tapas drafts a statement of the value delivered, measured against your baseline cost, which is the cost of a task before agents started. Your named person confirms or corrects it
- Payment
- After confirmed outcomes, the business decides whether to enter a commercial agreement
How a business relationship is set up
Tapas runs one central control plane. At your premises, edge boxes pull their agent code, and the site's root edge box keeps your event records to begin with. The global platform connects only to the control plane, never directly to an edge box.
- No inbound connectionsEach box polls outward for its instructions. The design does not require opening inbound ports on the business's premises.
- Updates carry agent code onlyUpdates contain Tapas-authored code and configuration, and no partner data. Agent templates are the open-source core logic agents start from; a configuration, approved by your named person, adapts a template to one task in your plan.
- Identity checked at first connectionEach box is designed to carry a credential issued before shipment and a firewall that blocks inbound traffic. It is provisioned only after presenting that credential.
- Same rules for any hardwareWhether Tapas owns the box or the partner does, the same rules apply. Only ownership and exit steps differ.
- One box is enough to startA single edge box is allowed today. The site's root edge box keeps your event records to begin with.
- Your records stay on your premisesThe authoritative event records are kept on your edge box. Only catalogued, typed values may be sent from your premises.
The Plan of Record
The Plan of Record answers two questions at any time: which plan is in force for a business function, and which outcomes were delivered under which version of it. A business function is a named, bounded part of your business that a plan is made for, and it outlives every plan written for it.
A complete plan, signed by the partner.
How a plan changes
- Fixed once proposedA revision can be edited only while in draft. Declined revisions are kept on record.
- One revision in forceApproving a new revision retires the previous one from the day the new one takes effect.
- Changes apply forwardA revision can take effect on a future date, not a past one.
- One live plan per functionA replacement plan starts only after the previous one closes.
Linking outcomes to a plan
Each agent action is linked once to the revision in force when it happened. The link is not recalculated later. The ontology calls this outcome attribution.
| In plan | Counts toward the plan's measures and the outcome value. |
| Not in revision scope | The item was removed or not yet added. Recorded; not counted toward outcome value. |
| No revision in force | No approved plan applied at that time. Recorded; not counted toward outcome value. |
Rules that apply to everyone
No agent action can be recorded without valid, unrevoked onboarding terms.
Access scope: an action outside what the onboarding terms cover is flagged, excluded from outcome value and reviewed.
Plan scope: an outcome outside the revision in force is recorded but not counted, and it is not sent for review on that account.
Every alert is an action that Tapas drafts and a named person at the business releases. No action runs on its own: autonomous action is refused for every action type. Where something must be filed or paid to an authority, Tapas drafts it and your named person files and pays. Tapas never asks for, holds or stores the logins you keep for your own accounts.
A plan's content changes only in a draft revision, and a revision takes effect only when your named person approves it.
People see only what their assigned relationships have agreed may be seen.
Either party can end access at any time, effective within 24 hours. The business needs no reason; Tapas always states its reason. Revoking access closes every plan under it, with proof that data was cleared. Pausing a plan leaves access unchanged.
Each agent action has an event record showing what was done, whether it was in or out of scope, and its verification state: unverified, verified, disputed or expired. A named person at the business records the verification after the event, and the latest finding is the current state. The data and the action it records are metadata only. Findings about an event are recorded separately as verification records, and the event itself is not changed.
Every change to a plan is recorded as an event and needs a person's signature. That signature is the confirmation gate.
Terms used on the platform
No term matches. Try a shorter word, or clear the search.