Batoi Playbook: Get Started Guide
Use this guide if your team is starting with Playbook or wants to make workspace knowledge more reliable, reusable, and safe to share.
Open articlePlan, build, govern, secure, learn, and apply intelligence through one accountable digital delivery foundation.
Workspace owners, admins, builders, operators, analysts, reviewers, and adoption leaders using Batoi Platform.
Enter the authorized workspace through My Batoi and confirm that you have permission for the task, information, and decision involved.
You can choose the appropriate Platform capability; complete the current Build App Lifecycle with verified source, runtime, release, Guard, Govern evidence, and member-safe sharing outcomes; preserve accountable review; and recognize when additional authority or support is needed.
Use this guide if your team is starting with Playbook or wants to make workspace knowledge more reliable, reusable, and safe to share.
Open articleStructure an application delivery plan around outcomes, ownership, evidence, release conditions, and verification.
Open articleFollow the current 11-check Batoi Build App Lifecycle from App record and canonical source through verified deployment, evidence, Guard review, and optional member-safe sharing.
Open articleCreate the stable App record, creation profile, source intent, owner, and optional Core Project coordination used by Batoi Build.
Open articleFor an App using GitHub source mode, link its canonical repository and verify branch, synchronization, integrity, and delivery ownership.
Open articleRegister a bounded non-production target and verify its app context, public entry point, health route, and rollback boundary.
Open articleConnect the App to its approved sandbox data service with explicit access and change authority and no exposed connection details.
Open articleTurn business information requirements into a reviewable application data model.
Open articleEvaluate a proposed source or configuration change before promotion.
Open articlePublish an explicit reviewed revision, require a terminal run result, verify the deployment independently, and preserve Guard and Govern evidence.
Open articleCreate an approved project-sharing policy with explicit recipient, audience, redaction, visible sections, and member portal verification.
Open articleEvaluate an obligation, risk, approval, and evidence packet before recording an accountable decision.
Open articleCreate a policy statement with scope, authority, obligations, controls, and review ownership.
Open articleTranslate an applicable requirement into owned, reviewable operational obligations.
Open articleDescribe a risk consistently and decide proportionate treatment and review.
Open articleMove a consequential request through evidence-backed human authority.
Open articlePlan and record evidence that links a Build change to source, review, publish, deployment, Guard, approval, and controlled sharing.
Open articleEvaluate a defined scope against reviewed questions, evidence, and decision criteria.
Open articleSummarize material obligations, risks, decisions, evidence, and actions for accountable oversight.
Open articleReview security findings, evidence, treatment, and release gates before an application change is promoted.
Open articleBring an approved source repository into the security-assurance boundary.
Open articleCreate the reviewed starting point against which material security change is evaluated.
Open articlePrioritize vulnerabilities using evidence, exposure, exploitability, and application context.
Open articleProduce a component inventory and review dependency provenance and version risk.
Open articleEvaluate dependency, artifact, repository, and release provenance before promotion.
Open articleTurn release-specific Guard findings and policy thresholds into an explicit pass, block, or authorized exception.
Open articleRetain the material security and approval evidence for a release decision.
Open articleLearn how to open Batoi Learn, choose a practical lab, and follow a guided learning path from understanding to workplace application.
Open articleComplete a practical Batoi Learn lab, submit evidence for automatic assessment, and improve your work from criterion-level feedback.
Open articleComplete the core Batoi Learn AI labs and send supported learning artifacts to Govern or Build for explicit human review.
Open articleUse the private mastery portfolio, understand every workspace role in Learn, and delegate teaching through scoped Instructor, Supervisor, or Reviewer duties.
Open articleSelect a lab whose learning outcome and scenario match a real capability need.
Open articleUse criterion-level feedback and reflection to improve an assessable lab output.
Open articleUnderstand completed evidence, current mastery, gaps, and next learning priorities.
Open articleTurn governed workspace information into a concise briefing with traceable evidence and accountable follow-up.
Open articleAsk a bounded question that can be answered from permitted operational context.
Open articleLimit an intelligence task to information authorized for its user and purpose.
Open articleVerify important claims before using an AI-assisted output in operational work.
Open articleKeep consequential action under authorized human control.
Open articlePreserve proportionate evidence of how an AI-assisted decision was prepared and authorized.
Open articleUse governed AI assistance to summarize context or prepare work while preserving human authority.
Open articleTry a capability, task, or outcome with fewer words.