01.01
Business context
The work situation, not just a prompt.
Roles, sources, goals, screens, documents, history and limits that AI needs before it can help usefully.
Brevity Wiki
The terms behind controlled AI automation.
A short knowledge base for clients, teams and visitors who want to understand how Brevity talks about context, workflows, courses and governance.
This page is not a technical manual and not a marketing glossary. It is the shared language for a first pilot: what we inspect, what we build, and what stays deliberately human.
Context before actionEvidence before outputHuman approval where neededStart small, measure clearly
01 / Context Layer
Context Layer
The context layer connects real work to AI. It does not collect everything, only what a workflow actually needs.
01.02
Source map
Which source says what?
A map of the documents, systems, fields and people that matter for a process. Without it, automation stays blind.
01.03
Evidence trail
Why did this output happen?
A trace of sources, assumptions and decisions. It helps humans review AI outputs faster and more safely.
02 / Workflow
Workflow Design
Brevity does not automate the entire company at once. The first step is a recurring process with clear inputs, review points and decision criteria.
02.01
Pilot workflow
A small process with real value.
A bounded process that can be tested quickly: who uses it, which sources it needs, and what counts as a good result.
02.02
Approval point
Where a human decides.
A defined stop before an output becomes external, financial, legal or operationally effective.
02.03
No-go action
What AI may never do alone.
Blocked actions: payments, contract commitments, sensitive customer data, final decisions or anything without enough source evidence.
03 / Learning
Courses and Workshops
Courses give teams a shared base. Workshops and implementation sprints turn that base into real company work.
03.01
Course grant
Paid or manually approved access.
Course portal access is prepared through payment, invoice or admin grant. It is not opened through free public registration.
03.02
Certificate
Proof after course completion.
A certificate confirms that course modules were completed. It does not replace an external standard or professional qualification.
03.03
Workshop
Working on the real process together.
A workshop helps teams define use cases, sources, risks, review points and the first pilot clearly.
04 / Governance
Governance
Control is not a brake. It is what makes AI usable in companies: clear limits, logs, roles and honest uncertainty.
04.01
Human approval
People stay responsible.
AI can prepare, structure and suggest. For sensitive or effective steps, a human remains in the decision flow.
04.02
Privacy-first
Use only what is needed.
Brevity treats data access sparingly: which source is allowed, which information is necessary, and what must stay out of the workflow?
04.03
Operational readiness
Ready means tested.
A feature is only ready when auth, data, email, payments, roles and error states have been checked in the real flow.
Use the wiki as a starting point, not a substitute for analysis.
A good Brevity pilot starts with a real workflow, real sources and an honest boundary. Then we decide whether automation, course, workshop or portal access makes sense.