System: MWMS
Document Type: Checklist
Authority Level: MCR Source Of Truth
Status: Draft For MCR
Primary Location: MCR
Future Operational Destination: HeadOffice Brain, AIBS Brain, AI Manager, AI Employee Router, Brain Room, Course Absorption System, Content Brain, Offer Brain, Sales Brain, Creative Brain, Research Brain, Compliance Brain, Future AIBS Client Systems
Parent Page: HeadOffice
Owner: Martyn
Developer Boundary: No Development Action Authorized By This Page
Source Of Truth: MCR
Purpose
The purpose of this document is to define the MWMS AI Brain Build Implementation Checklist.
This checklist gives MWMS a practical step-by-step implementation path for building an AI Brain, context library, offer library, client Brain, AI Employee context base, or future AIBS client system.
MWMS must not build AI systems by jumping straight into prompts, assets, automations, or tools.
The correct build path is:
Prepare
Excavate
Construct
Activate
Build
Validate
Promote
Audit
Closeout
This checklist turns the AI Brain Build Sequence into an operational implementation checklist.
It helps MWMS confirm what has been done, what is missing, what can be used, what must remain draft, what requires review, and what should happen next.
Without this checklist, MWMS risks:
building from weak source material
creating context before evidence exists
creating assets before buyer and offer clarity exist
installing skills before procedures are clear
using draft context as active source truth
forgetting proof and claims control
skipping retired language checks
mixing client context with MWMS context
creating outputs without handoff or registry update
calling a Brain ready before it has passed readiness review
This checklist exists to keep AI Brain builds practical, sequenced, governed, and safe to scale.
Scope
This checklist applies to all MWMS Brain build and context build work.
This includes:
HeadOffice Brain
AIBS Brain
AI Manager
AI Employee Router
Brain Room
Course Absorption System
Newsletter Intelligence
Opportunity System
Offer Brain
Content Brain
Creative Brain
Sales Brain
Conversion Brain
Customer Brain
Research Brain
Affiliate Brain
Ads Brain
Compliance Brain
future AIBS client systems
This checklist applies when MWMS is building or improving:
AI Brains
client Brains
offer context libraries
client context libraries
AI Employee context bases
skill libraries
content systems
sales systems
ad systems
funnel systems
proof libraries
voice systems
workflow maps
context-driven asset systems
future AIBS client delivery packages
This checklist does not authorize technical development, plugin changes, Supabase changes, WordPress changes, automation wiring, publishing, client implementation, credential handling, file deletion, or M developer action.
Core Principle
The core principle of this checklist is:
Build the context before building the assets. Build the evidence before trusting the context. Build the review gates before scaling the system.
MWMS AI Brain build work must move in a disciplined order.
The system should not ask AI Employees to perform high-value work until the right context exists.
The system should not treat context as approved until it has been reviewed.
The system should not treat outputs as source truth until they have been promoted properly.
Implementation Stages
MWMS AI Brain build implementation uses nine stages.
Stage 1: Prepare Source Material
Stage 2: Excavate Intelligence
Stage 3: Construct Context Library
Stage 4: Activate Context For Use
Stage 5: Build Assets Or Skills
Stage 6: Validate Output
Stage 7: Promote Or Park Material
Stage 8: Audit And Maintain
Stage 9: Handoff And Closeout
Each stage should be checked before moving into stronger usage.
Stage 1: Prepare Source Material
Purpose
The purpose of this stage is to gather and classify the raw material needed before building context, assets, skills, or client systems.
Checklist
Confirm the build target is clear.
Identify whether the build is for:
internal MWMS Brain
offer library
client Brain
campaign system
skill system
asset system
course absorption output
future AIBS client package
Confirm the owning Brain.
Confirm supporting Brains.
Gather available source material.
Classify source material by type.
Separate raw material from draft context.
Identify source locations.
Identify source strength.
Identify sensitive material.
Identify client-specific material.
Identify technical evidence if developer guidance may be needed.
Identify missing source material.
Record what source material can support.
Record what source material cannot support.
Decide whether enough source material exists to continue.
Required Outputs
Source material set
Evidence inventory
Missing material list
Owning Brain
Initial build purpose
Boundary notes
Possible Decisions
Ready For IP Excavation
Needs More Source Material
Needs Transcription
Needs Human Review
Needs Client Approval
Needs Technical Confirmation
Park For Later
Ignore
Stage 1 Drift Risks
Do not build from memory alone.
Do not treat raw material as approved context.
Do not confuse sales-page hype with strong evidence.
Do not use client material outside its boundary.
Do not give exact developer instructions without current technical evidence.
Stage 2: Excavate Intelligence
Purpose
The purpose of this stage is to extract reusable intelligence from source material before creating structured context files.
Checklist
Extract contrarian stances.
Extract methodology and process.
Extract expert thinking.
Extract buyer language.
Extract buyer objections.
Extract proof candidates.
Extract voice patterns.
Extract differentiation signals.
Extract retired language candidates.
Extract compliance-sensitive language.
Extract workflow patterns.
Extract possible skill candidates.
Extract content opportunities where relevant.
Mark evidence strength for each extracted item.
Separate evidence-based points from assumptions.
Flag missing evidence.
Flag weak source support.
Flag material that should be ignored.
Required Outputs
Contrarian Stances
Methodology Notes
Expert Thinking Notes
Buyer Language Extract
Objection Extract
Proof Candidate List
Voice Notes
Differentiation Notes
Retired Language Candidates
Missing Evidence List
Possible Skill Candidates
Possible Context Updates
Possible Decisions
Ready For Context Library Construction
Needs More Source Material
Needs Human Review
Needs Research Verification
Needs Client Review
Needs Compliance Review
Park For Later
Ignore
Stage 2 Drift Risks
Do not invent founder beliefs.
Do not invent methodology.
Do not invent buyer language.
Do not invent proof.
Do not promote extracted insights without review.
Do not absorb weak course material just because it exists.
Stage 3: Construct Context Library
Purpose
The purpose of this stage is to convert extracted intelligence into structured context files that AI Employees can use.
Checklist
Confirm the context library type.
Possible types:
MWMS Brain Context Library
Offer Context Library
Client Context Library
Campaign Context Library
AI Employee Context Pack
Skill Context Base
Create or update required context files.
Core context files may include:
Right-Fit Client Profile
Offer Profile
Voice Architecture
Differentiation Profile
Objection Library
Methodology Map
Expert Thinking Rules
Customer Language Bank
Proof Library
Brand Visual Style
Retired Language
Compliance Notes
Client Approval Rules where relevant
Client Workflow Map where relevant
Tool Boundary Notes where relevant
Assign file status.
Possible statuses:
Draft
Under Review
Approved
Active
Restricted
Stale
Retired
Archived
Rejected
Confirm source-of-truth location.
Check duplicate context risk.
Separate active context from draft material.
Separate raw material from context files.
Separate output assets from context files.
Separate client context from MWMS context.
Confirm proof approval status.
Confirm retired language is visible.
Confirm missing context is labelled.
Required Outputs
Structured context library
File status labels
Source-of-truth location
Missing context list
Proof status
Retired Language file where relevant
Client boundary notes where relevant
Possible Decisions
Draft Context Created
Manual-Use Context Ready
Assisted-Use Context Ready
Operational Context Ready
Client-Ready Context Pending Review
Needs Missing Files
Needs Cleanup
Needs Review
Stage 3 Drift Risks
Do not treat draft context as active.
Do not create duplicate active files.
Do not mix client context with MWMS context.
Do not add unapproved proof as active proof.
Do not hide retired language in archive only.
Do not create bloated context libraries with irrelevant material.
Stage 4: Activate Context For Use
Purpose
The purpose of this stage is to select the right context for a specific task before AI Employees create outputs, run skills, or build assets.
Checklist
Identify the current task.
Identify the owning Brain.
Identify supporting Brains.
Confirm current user instruction.
Confirm active context library.
Select only relevant context files.
Confirm selected files are approved or mark draft status.
Prepare an AI Context Pack if needed.
Include required standards.
Include forbidden actions.
Include missing context.
Include risk level.
Include human review requirement.
Include output destination.
Include validation requirement.
Include handoff destination.
Confirm whether work is:
draft only
manual use
assisted use
operational use
client review use
not ready
Required Outputs
Task-specific Context Pack
Selected context file list
Relevant standards list
Risk level
Human review requirement
Output destination
Validation requirement
Possible Decisions
Proceed
Proceed In Draft Mode
Pause And Ask
Park For Later
Stop
Stage 4 Drift Risks
Do not use memory instead of approved context.
Do not load unrelated context.
Do not skip retired language for messaging tasks.
Do not use archive files as active context.
Do not use client context outside the client boundary.
Do not proceed when required context is missing for high-risk work.
Stage 5: Build Assets Or Skills
Purpose
The purpose of this stage is to create business outputs, AI skills, context-driven assets, or internal MWMS pages from activated context.
Checklist
Identify whether this is a manual build or skill build.
If manual build, confirm:
task is one-off, custom, exploratory, or not yet procedural
context is activated
output destination is clear
review is required where relevant
If skill build, confirm:
task repeats
method is clear
input is defined
context is defined
output is defined
validation is defined
handoff destination is defined
forbidden actions are defined
installation status is conservative
If asset build, confirm asset objective.
Possible assets:
lead magnet
webinar
landing page
sales page
email sequence
VEO3 script
ad script
client report
sales script
content brief
offer evaluation
MCR page
If MCR page, confirm:
document type
parent page
authority level
status
purpose
scope
rules
governance role
relationships
drift protection
architectural intent
change log
change impact declaration
employee impact check
Required Outputs
Draft asset
Draft skill
Draft MCR page
Draft context file
Manual build output
Skill record
Asset package
Possible Decisions
Continue To Validation
Needs More Context
Needs Human Review
Needs Client Review
Needs Compliance Review
Needs Proof
Park
Reject
Stage 5 Drift Risks
Do not create template-first assets without context.
Do not invent proof.
Do not invent buyer language.
Do not create sales assets without objections.
Do not create public-facing assets from draft context.
Do not install a skill just because it was written.
Do not imply automation from skill creation.
Stage 6: Validate Output
Purpose
The purpose of this stage is to check whether the created output matches context, standards, risk rules, and intended use.
Checklist
Validate against current user instruction.
Validate against document structure where relevant.
Validate against owning Brain rules.
Validate against selected context files.
Validate buyer accuracy.
Validate offer accuracy.
Validate voice alignment.
Validate differentiation.
Validate objections.
Validate proof.
Validate claims.
Validate retired language.
Validate compliance notes.
Validate client boundary where relevant.
Validate output format.
Validate handoff destination.
Validate registry impact.
Validate employee impact.
Validate whether output is still draft.
Validation Questions
Is the buyer correct?
Is the offer correct?
Is the voice correct?
Is proof approved?
Are claims safe?
Are objections handled?
Is retired language avoided?
Is the output too generic?
Is the output aligned with MCR structure where relevant?
Is review required before use?
Is any context missing?
Is any assumption hidden?
Required Outputs
Validation result
Revision notes
Review requirement
Risk notes
Approval status recommendation
Possible Decisions
Approved For Draft Use
Needs Revision
Needs Human Review
Needs Client Review
Needs Compliance Review
Needs Research Verification
Needs Proof
Park
Reject
Stage 6 Drift Risks
Do not validate only for grammar.
Do not approve output because it reads well.
Do not ignore missing proof.
Do not ignore retired language.
Do not treat AI draft output as source truth.
Do not skip client review for client-facing work.
Stage 7: Promote Or Park Material
Purpose
The purpose of this stage is to decide what happens to the output after validation.
Checklist
Identify current authority level.
Possible levels:
Raw Material
Extracted Insight
Draft Context
Reviewed Context
Approved Context
Active Source Truth
Canon Context
Decide destination.
Possible destinations:
existing context file update
new context file
MCR page
skill record
checklist
framework
protocol
rule
asset library
client library
archive
parking system
reject
Check promotion criteria.
Promotion criteria:
source known
purpose clear
owning Brain clear
destination clear
evidence strength known
duplicate risk checked
review complete where needed
proof status clear
client boundary clear
compliance risk checked where relevant
registry impact identified
Decide whether material should be:
promoted
parked
archived
restricted
retired
rejected
sent for review
Required Outputs
Promotion decision
Authority level
Destination
Registry impact
Review requirement
Next action
Possible Decisions
Promote To Existing Context File
Create New Context File
Create MCR Page
Create Skill Record
Create Checklist
Park For Later
Archive
Reject
Needs More Evidence
Needs Review
Stage 7 Drift Risks
Do not promote raw material directly to active context.
Do not promote AI drafts as source truth.
Do not create duplicate MCR pages.
Do not promote client material into MWMS context without approval.
Do not promote proof without claim boundaries.
Do not leave useful output without destination.
Stage 8: Audit And Maintain
Purpose
The purpose of this stage is to keep Brains, context libraries, skills, assets, and client systems current after creation.
Checklist
Assign audit cadence.
Possible audit cadence:
monthly light check
quarterly full audit
event-based audit
Identify update triggers.
Update triggers may include:
offer change
buyer change
voice change
proof change
methodology change
new objections
client feedback
campaign data
compliance issue
ad disapproval
repeated human correction
AI output drift
client approval change
Check for decay signals.
Decay signals may include:
generic AI output
old language returning
wrong offer promise
stale proof
duplicate files
draft files used as active
client context leakage
skills producing wrong format
human rewriting instead of polishing
Run dependency review when context changes.
Check whether affected items need:
update
restriction
retirement
archive
review
registry change
employee behaviour update
Required Outputs
Audit status
Decay signals
Required updates
Next review date
Kaizen learning
Possible Decisions
Current
Minor Refresh Required
Major Refresh Required
Split Library
Merge Library
Park
Retire
Archive
Human Review Required
Stage 8 Drift Risks
Do not let context decay silently.
Do not ignore repeated corrections.
Do not keep stale files active.
Do not keep expired proof active.
Do not allow retired language to return.
Do not let client files drift into general context.
Stage 9: Handoff And Closeout
Purpose
The purpose of this stage is to close the build cleanly so MWMS knows what was created, what is ready, what needs review, what is parked, and what happens next.
Checklist
Record creation summary.
List pages created.
List pages updated.
List context files created.
List skills created.
List assets created.
List pages parked.
List material ignored.
List material needing review.
Declare current status.
Identify registries requiring update.
Identify Brain impact.
Identify AI Employee impact.
Identify review requirements.
Identify risk status.
Identify parked or deferred work.
Identify next action.
Identify restart point.
Confirm developer boundary.
Confirm M boundary where relevant.
Confirm no unauthorized development action is implied.
Required Outputs
Closeout summary
Registry update list
Employee impact notes
Review status
Parked item list
Next action
Restart point
Possible Decisions
Build Complete
Draft Complete
Review Required
Registry Update Required
Parked
Paused
Needs More Source
Course Closed
Stage 9 Drift Risks
Do not end with no next action.
Do not forget registry impact.
Do not call drafts active.
Do not forget employee impact.
Do not forget parked work.
Do not imply development action.
Do not lose restart point.
Implementation Readiness Checklist
Before a Brain, context library, skill set, or client system moves into stronger use, confirm the following.
Source Material
Source material collected.
Source material classified.
Source material location recorded.
Evidence strength marked.
Missing material listed.
Client-specific material isolated.
Sensitive material identified.
Intelligence Extraction
Contrarian stances extracted.
Methodology extracted.
Expert thinking extracted.
Buyer language extracted.
Objections extracted.
Proof candidates extracted.
Voice patterns extracted.
Retired language candidates extracted.
Context Library
Right-Fit Client Profile created where needed.
Offer Profile created where needed.
Voice Architecture created where needed.
Differentiation Profile created where needed.
Objection Library created where needed.
Methodology Map created where needed.
Expert Thinking Rules created where needed.
Customer Language Bank created where needed.
Proof Library created where needed.
Retired Language created where needed.
Compliance Notes created where needed.
File statuses assigned.
Context Readiness
Context readiness level assigned.
Missing context labelled.
Draft context marked.
Manual-use context defined.
Assisted-use context defined where relevant.
Operational context approved where relevant.
Client-ready context reviewed where relevant.
Skills
Skill candidates identified.
Manual versus skill decision made.
Existing skill duplication checked.
Skill input defined.
Skill context defined.
Skill procedure defined.
Skill output defined.
Skill validation defined.
Skill forbidden actions defined.
Skill handoff destination defined.
Skill installation status assigned.
Assets
Asset objective clear.
Buyer clear.
Offer clear.
Proof status clear.
Voice clear.
Objections considered.
Retired language checked.
Compliance notes checked.
Output destination clear.
Review requirement clear.
Proof And Claims
Proof Library checked.
Claim strength matched to proof.
Unsupported claims removed or softened.
Proof gaps labelled.
Client proof approval checked.
Affiliate proof reviewed where relevant.
Paid traffic proof reviewed where relevant.
Client Boundary
Client name clear.
Client context isolated.
Client privacy level assigned.
Client approval status known.
Client proof usage permission known.
Client voice approval known.
Client report review gate known.
Client assets marked draft until approved.
Review And Approval
Human review requirement clear.
HeadOffice review required where relevant.
Brain owner review required where relevant.
Client review required where relevant.
Compliance review required where relevant.
Technical confirmation required where relevant.
Promotion And Registry
Promotion decision made.
Authority level assigned.
Destination confirmed.
Duplicate risk checked.
Registry impact identified.
Change log requirement identified.
Employee impact check included.
Audit And Closeout
Audit cadence assigned.
Update triggers listed.
Dependency review required where relevant.
Closeout completed.
Restart point recorded.
Next action clear.
Implementation Status Levels
MWMS uses the following implementation status levels.
Not Started
No meaningful source material or build work has begun.
Source Intake Started
Source material is being gathered and classified.
Extraction In Progress
Source material is being analyzed for reusable intelligence.
Draft Context Created
Context files exist but are not approved.
Manual Use Ready
Context supports human-reviewed manual work.
Assisted Use Ready
Context supports AI-assisted workflows with validation.
Operational Use Ready
Context is approved for internal active use.
Client Review Ready
Client-specific output is ready for client review.
Client Use Ready
Client-specific system has passed required approval gates.
Audit Required Before Use
System was once active but may now be stale.
Parked
Useful but not active now.
Retired
No longer in use.
Implementation Decision Template
Use this template when checking a build.
Build Name:
Build Type:
Owning Brain:
Supporting Brains:
Current Stage:
Current Status:
Source Material Ready:
Intelligence Extracted:
Context Library Built:
Context Level:
Skills Required:
Assets Required:
Proof Status:
Voice Status:
Client Boundary:
Review Required:
Missing Context:
Risk Level:
Registry Impact:
Employee Impact:
Audit Requirement:
Next Action:
Restart Point:
Notes:
Minimum Implementation Decision
Use this for quick checks.
Build:
Stage:
Status:
Missing:
Risk:
Next Action:
Restart Point:
Common Failure Modes
MWMS must prevent:
building from memory alone
skipping source intake
extracting weak material as if strong
creating assets before context exists
creating context from assumptions
using draft context as active
installing skills too early
creating duplicate pages
ignoring proof gaps
ignoring retired language
ignoring client approval
skipping validation
skipping promotion review
forgetting registry impact
forgetting closeout
Governance Role
HeadOffice owns the MWMS AI Brain Build Implementation Checklist.
HeadOffice is responsible for:
ensuring build sequence is followed
preventing premature activation
ensuring source material is gathered
ensuring context levels are assigned
ensuring review gates are respected
ensuring promotion decisions are governed
ensuring registries are updated
ensuring closeout is completed
ensuring M’s active development boundary is protected
Individual Brains are responsible for applying this checklist within their domain.
AIBS Brain governs future client system implementation.
Offer Brain governs offer context implementation.
Content Brain governs content system implementation.
Sales Brain governs sales system implementation.
Creative Brain governs creative system implementation.
Research Brain governs evidence quality.
Compliance Brain governs claims and policy risk.
Relationship To Other MWMS Standards
This checklist supports and must align with:
MWMS Document Structure Standard
MWMS Source Material Intake And Evidence Inventory Checklist
MWMS Missing Context And Evidence Gap Handling Rule
MWMS Minimum Viable Context Library Rule
MWMS Client IP Excavation Framework
MWMS Offer Context Library Standard
MWMS Context Library Governance And Folder Map Standard
MWMS Context File Promotion And Approval Protocol
MWMS Context Change Propagation And Dependency Map Protocol
MWMS Context Library Hygiene And Retired Language Rule
MWMS AI Context Activation And Usage Protocol
MWMS AI Context Pack Template Standard
MWMS Context-Driven Asset Builder Framework
MWMS Voice Architecture And Brand Language Standard
MWMS Right-Fit Client And Offer Profile Standard
MWMS Differentiation And Objection Library Standard
MWMS Proof Library And Claims Control Standard
MWMS AI Skill Brainstorm And Prioritization Framework
MWMS Manual Build Versus Skill Build Decision Rule
MWMS AI Skill Installation And Usage Protocol
MWMS AI Brain Readiness Review Checklist
MWMS AI Brain Audit And Decay Prevention Framework
MWMS AI Brain Page And Asset Registry Standard
MWMS AI Brain Build Handoff And Closeout Standard
MWMS Client Context Isolation And Privacy Boundary Standard
MWMS Client Approval And Review Gate Protocol
MWMS Brain Routing Rule
MWMS MCR Promotion To Brain Protocol
MWMS Architecture Registry
AIBS Brain Canon
This checklist provides the practical implementation layer that connects the related source, context, skill, asset, review, promotion, audit, and closeout standards.
Drift Protection
This checklist protects MWMS from:
unsequenced Brain builds
empty-context AI work
premature asset creation
draft context overreach
unapproved proof
client context leakage
skill sprawl
missing validation
missing promotion control
missing registry updates
missing closeout
future AIBS client systems built on weak foundations
Any AI Brain, context library, client Brain, skill set, or system build that skips this implementation checklist should be treated as an implementation drift risk.
Architectural Intent
The architectural intent of the MWMS AI Brain Build Implementation Checklist is to make AI Brain construction practical, repeatable, and governable.
MWMS is building a large ecosystem of Brains, context libraries, AI Employees, skills, assets, and future AIBS client systems.
That ecosystem needs a clear build checklist that tells the system what to do next and what must not be skipped.
The long-term goal is that every serious AI Brain build can answer:
What are we building?
What source material exists?
What intelligence was extracted?
What context files were created?
What context level exists?
What can be used now?
What remains draft?
What skills are needed?
What assets are needed?
What proof is approved?
What review is required?
What can be promoted?
What needs audit?
What registry updates are required?
What is the next action?
When MWMS can answer these questions consistently, AI Brain construction becomes faster, safer, cleaner, and easier to scale across internal Brains and future AIBS client systems.
Change Log
v1.0 — Initial Draft
Created the MWMS AI Brain Build Implementation Checklist as the practical implementation checklist for building AI Brains, context libraries, offer libraries, client Brains, AI Employee context bases, skill systems, asset systems, and future AIBS client systems.
This checklist defines the nine-stage implementation process: Prepare Source Material, Excavate Intelligence, Construct Context Library, Activate Context For Use, Build Assets Or Skills, Validate Output, Promote Or Park Material, Audit And Maintain, and Handoff And Closeout.
It also defines readiness checks, implementation status levels, decision templates, failure modes, governance role, drift protection, and architectural intent.
Change Impact Declaration
Pages Created:
MWMS AI Brain Build Implementation Checklist
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
HeadOffice Page Registry
AIBS Brain Page Registry
Course Absorption Page Registry
Offer Brain Page Registry
Content Brain Page Registry
Sales Brain Page Registry
Creative Brain Page Registry
Research Brain Page Registry
Compliance Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
Employee Impact Check
Employees impacted:
HeadOffice Manager Employee
AI Manager
AI Employee Router
Brain Room Assistant
Course Absorption Agent
Context Library Builder
Client IP Excavator
Skill Auditor
Offer Strategist Employee
Content Planner Employee
Creative Strategist Employee
Sales Strategist Employee
Research Analyst Employee
Compliance Reviewer Employee
AIBS Architect Employee
Required behaviour updates:
AI Employees must follow the Prepare, Excavate, Construct, Activate, Build, Validate, Promote, Audit, and Closeout stages when implementing AI Brain, context library, client Brain, skill, or future AIBS system builds.
AI Employees must not create high-value assets, install skills, promote context, or declare readiness before required source material, context level, proof status, review gates, and output destination are clear.
AI Employees must identify implementation stage, current status, missing context, risk level, registry impact, employee impact, audit requirement, next action, and restart point during significant build work.
AI Employees must use AIBS Brain as the canonical Brain name in MCR references, registry references, parent fields, future operational destinations, and employee impact sections.
END MWMS AI BRAIN BUILD IMPLEMENTATION CHECKLIST v1.0