A strict performance benchmark where the total weight of a single-page website must not exceed 1 megabyte to minimize bandwidth and energy usage.
The permanent deletion of all project data from the provider’s system 48 hours after handover.
The client’s mandatory responsibility to remove the lab’s technical permissions immediately after the handover.
The formal process of changing account ownership for third-party tools (like Forms or Analytics) from the lab to the client.
The principle that the client must maintain primary ownership and administrative control of all technical accounts (Domain, Hosting, Analytics).
A coaching philosophy focused on increasing the user’s direct power over their tools rather than fostering consultant dependency.
A mandatory check verifying that all non-decorative images include descriptive text for both SEO and accessibility.
The requirement for every image and icon to have descriptive “alt” attributes for both search engine optimization and accessibility.
A standard requiring images and logos to be clear, optimized, and free from cluttered backgrounds.
A specific folder structure (Logos, Hero_Images, Service_Photos) that clients must follow to ensure systematic data transfer.
Communication restricted to text-based channels without real-time meetings or calls.
A clause stating that purchasing or downloading a blueprint constitutes 100% agreement with all laboratory rules.
The policy where the underlying code logic and templates remain the permanent intellectual property of Thet.
The technical process of ensuring that meta tags for both language versions are conceptually and structurally aligned.
The mandatory technical integration of lang attributes and hreflang tags for dual-market (Myanmar/English) targeting.
A visual pacing strategy that guides the user journey by alternating between dark “immersive” and light “informational” sections.
A technical constraint requiring all brand styles to be defined in global variables, forbidding inline overrides.
Periodic assessments of projects and goals to ensure they remain in alignment with the laboratory’s core values.
The fundamental “Operating Constitution” or Source of Truth that governs all lab operations and hard constraints.
A professional identity style that blends the technical precision of an engineer with high-end, reductive design aesthetics.
A business value that prioritizes clear, predictable results over the ability to make infinite, non-standard changes.
A design rule ensuring that no primary piece of information is deeper than three clicks away from the landing page.
A design standard ensuring that a user can reach any primary action or piece of information within a maximum of three clicks.
A requirement for clients to agree to the permanent termination of a project once the 48-hour revision window closes.
A summary-first writing style optimized for digital reading that encourages users to explore deeper for more detail.
A standardized Google Doc template used to gather all textual content for each website section before any technical work begins.
A strict rule where no technical implementation begins until 100% of the content is approved.
The deliberate use of vast high-contrast color expanses (Forest Green vs. Near-White) to present digital solutions as sculptures.
Prioritizing high-depth, text-based project discussions over shallow, real-time digital “pings.”
The specific procedure (SOP-03) of gathering all source code, documentation, and access keys into a single secure Zip folder for the client.
The balance point where Cinematic visual aesthetics perfectly meet functional engineering.
A technical choice to build systems without backend databases to ensure permanent speed, portability, and security.
The requirement for a client to be fully prepared to make final decisions before starting a session.
The audit step where the quantity of text is checked against the layout’s capacity to prevent visual clutter and information overload.
A coaching method that teaches the client how to identify and fix the root cause of a problem rather than relying on a quick fix.
The routine practice of reviewing and optimizing digital assets and cloud storage to reduce mental and system overhead.
The primary goal of the DWY tier, ensuring the client gains the specific skills needed to manage their own digital system.
A comprehensive one-year tracking system used to manage revenue targets, location databases, and annual growth goals.
The requirement for all service registrations to be tied to the client’s legal identity and verified payment methods.
A visual organization of project ideas and assets created using Affinity Diagramming techniques before the build begins.
The requirement to document every process and instruction in writing before assets are handed over.
Self-serve digital products or blueprints that clients implement themselves.
A full execution service where the provider builds the entire system for the client.
A guided collaboration/coaching model where the provider and client build the system together.
The requirement that Burmese and English texts maintain conceptual and structural alignment across the bilingual interface.
The fluctuation of methodology intensity based on the latest experimental findings regarding digital efficiency and speed.
The core doctrine of prioritizing the conservation of mental energy over revenue growth or social visibility.
A training method used during handover to help clients recognize their system as a strategic asset rather than a collection of code.
The mandatory vetting process used to evaluate if a client’s business model aligns with the lab’s values before work begins.
Relying on hard data and case studies to demonstrate value rather than using aggressive sales tactics.
The rigid “First-In, First-Out” sequencing system that determines the priority of laboratory implementation slots.
The ethical principle ensuring that the effort expended by the lab is balanced by the client’s payment and readiness.
Logic-based mechanisms built into the website to screen potential clients and projects for alignment before allowing contact.
The delivery of a clean, audited, and offline-ready archive containing the entire website’s HTML, CSS, and optimized assets.
The rule stating that any engagement with the laboratory constitutes a 100% legally binding acceptance of the V8.1 Operating System rules.
A strategic savings and investment benchmark used to ensure the long-term sustainability of the independent lifestyle.
A front-end architecture that uses locked heights (100vh) to create non-scrolling, single-screen experiences on desktop.
The specific technical rules and operational behaviors that a digital system must follow to be considered complete.
The philosophical mandate for clients to take full responsibility for the growth and maintenance of their own digital ecosystem.
A mandatory content verification step to establish the physical or digital outreach limits of a client’s services.
The non-negotiable set of rules (vanilla code, no heavy frameworks, no external fonts) used to reduce the carbon footprint of digital assets.
A commitment to building high-performing, low-tech digital systems that minimize carbon footprints and ecological impact.
The final email or document where the client confirms they have received all assets and that the laboratory’s access can be revoked.
The philosophical alignment that a project’s success is a result of the client’s own proactive decisions and readiness.
Non-negotiable technical limitations, such as the total exclusion of heavy frameworks or unnecessary JavaScript.
Once project assets are submitted, no further changes or revisions are accepted before the build.
A post-launch roadmap phase involving manual search engine submission and the use of static sitemaps.
Managing search engine visibility through manual indexing and lean metadata rather than heavy dynamic plugins.
A design rule restricting hero titles to one or two lines to maintain the balance of the Zen Layout.
A design rule restricting headlines to one or two lines to preserve the minimalist aesthetic of the Zen Layout.
The mandatory use of language tags to correctly target search engine results for both Myanmar and English-speaking audiences.
Technical code tags used to tell search engines which language version of a page to show to specific international audiences.
The core doctrine defining Thet as an independent “Calm Digital Laboratory” rather than a traditional agency.
The direct sense of control a user experiences during real-time interaction with a minimalist digital interface.
High-impact areas of the website using the primary deep forest green background and white text for product showcases.
The foundational functional reasoning applied to every technical choice made within the laboratory’s sprint.
Defining specific earnings channels, such as Training or Web Development, to track business model performance.
A code quality requirement for clean, standardized nesting and the removal of all developer comments or “dead code” before handover.
A KPI measuring how few support tickets a client submits after the handover process is completed.
A 15-minute technical briefing provided during handover to teach the client how to perform basic content edits without a developer.
The systematic process of organizing website content and hierarchy into a logical sitemap based on business objectives.
Calm, readability-focused areas using neutral gray or light green backgrounds with dark text for data and text blocks.
The mandatory permanent deletion of client passwords and sensitive technical data from the lab’s internal systems 48 hours after handover.
A specific component logic used to display samples of digital products (Blueprints) without loading a full inventory list on the primary page.
A layout strategy that removes all borders, textures, and gradients, relying entirely on spacing to create structure.
A standardized document within the content folder used to track and organize target keywords in both Myanmar and English.
A strategic principle used to reject complex technologies that add more maintenance debt than actual business value.
The mandatory use of width and height attributes for all media to ensure page stability during loading.
The foundational principle of Essentialism focusing on the “vital few” high-impact tasks while eliminating the “trivial many.”
A personalized system design integrating professional skills with minimalism and essentialism to enhance purpose-driven living.
Prioritizing highly specific multi-word search phrases that indicate a strong intent to engage or purchase.
A typographic style using system fonts with specific line-heights and negative tracking to convey directness and confidence.
A framework ensuring the website effectively promotes the product, pricing, placement, and promotion of a business.
A quality check ensuring that Page Titles, Descriptions, and Open Graph tags are technically accurate and aligned with the business strategy.
A quality control step ensuring meta titles, descriptions, and Open Graph tags are technically accurate and strategically aligned.
A payment structure where the client pays after the completion of specific service modules.
A design philosophy where the interface intentionally retreats to honor the clarity and integrity of the solution.
A classification for potential clients who do not respect boundaries, cannot make decisions, or require constant technical dependency.
A design methodology that starts with the smallest screen size to ensure the highest business priorities are addressed first.
The automated transition of a fixed desktop layout into a scrollable vertical flow for mobile devices.
The practice of structuring life into independent modules (e.g., Coaching, Development, Health) that function separately but integrate seamlessly.
The protocol stating that post-closure technical help is not included and must be handled independently by the client.
A system-driven philosophy where agency is found in the architectural logic rather than a central personality or “self.”
A marketing approach that focuses entirely on the inherent value proposition and ignores pressure tactics or artificial scarcity.
The rigid set of legal and operational rules governing the sale and use of AI-generative digital models.
The practice of using digits (e.g., 01_Admin, 02_Clients) to control the order of files and folders in the Google-Only Ecosystem.
A methodology where the entire build and launch are completed within a single 8-hour workday.
The skeletal role responsible for system integrity, creating SOPs, and ensuring no rules (like Content-First) are violated.
The practice of manually adjusting weights and letter-spacing to mimic high-end typography using default system-ui fonts.
Progressive Web App optimization for mobile-like performance on a website.
The mandatory Google PageSpeed Insights score required for every project before it can pass the final technical audit.
A technical benchmark requiring a Google PageSpeed Insights score of at least 90.
A readability constraint limiting text blocks to a maximum of four lines to ensure optimal scannability for users.
A readability constraint that restricts blocks of text to a maximum of four lines of code.
A pricing model where the client decides the payment amount based on value.
Transitioning from a state where the interface is unnoticed (transparency) to one where the underlying structure is understood (opacity).
A discovery phase method used to create a granular, high-fidelity description of a target user persona’s daily habits and needs.
A screening criterion requiring projects to have a meaningful and ethical impact on their users or community.
The main call-to-action (CTA) button, specifically designed to be the user’s singular most important interactive destination.
The use of lightweight, cookie-less tracking tools that analyze user behavior without exploiting personal data or requiring consent banners.
A development philosophy that ensures core functionality works on static HTML/CSS before adding JavaScript enhancements.
Standard procedures designed to replace inefficient traditional business habits with logic-based digital workflows.
The mandatory practice of logically testing and validating business strategies before any technical implementation begins.
Specific behavioral indicators (vague project details, rush pressure, or payment avoidance) that trigger an immediate project rejection.
A mandatory coding standard requiring all file paths to be relative (e.g., /assets/img/) to ensure the system remains portable and independent of hosting environments.
A mandatory coding standard that ensures the website remains functional regardless of the hosting environment or folder depth.
Prioritizing the use of proven standards and successful templates over starting from scratch for every project.
A standard for folder naming and file organization that allows the laboratory to perform instant financial reporting.
The practice of setting financial goals that prioritize stability and energy protection over aggressive business scaling.
A framework that ranks project goals based on being Specific, Measurable, and Realistic to ensure tangible business impact.
Quantitative goals, such as achieving a specific PageSpeed score, used to measure the effectiveness of a project.
A structured set of Standard Operating Procedures (SOP-01 to SOP-06) governing the workflow.
A strategic post-launch roadmap task to integrate a website URL with global and local business profiles.
Subtle, text-based navigation used for supporting resources like agreements or policies to avoid distracting from the primary goal.
The verification process ensuring that content is provided for all six mandatory architectural sections defined in Memory 6.3.
A coding discipline where design elements are mapped directly to HTML5 semantic tags to eliminate bloated class names.
Prioritizing HTML5 semantic tags over excessive class names or JavaScript.
A front-end architecture using a fixed viewport to eliminate scrolling on desktop/tablet devices.
The practice of strictly enforcing asynchronous communication to protect the quiet space required for deep, solitary work.
The state of maintaining absolute authority over one’s own time, technical tools, and digital destiny.
The lab’s absolute authority over project schedules, specifically ignoring client-driven urgency or external deadlines.
The development of mental discipline and professional resilience through the consistent application of laboratory SOPs.
The manual creation and submission of XML sitemaps to search engines for database-free websites.
Building websites using only clean HTML and CSS to ensure speed and simplicity.
A price bracket used as a psychological filter to ensure mutual value between the laboratory and the client.
A coaching and AI interaction style designed to enhance the user’s agency and foster long-term self-sufficiency.
The process where knowledge from every completed project is fed back into the core system to reduce future complexity.
The practice of integrating knowledge gained from every project back into the core system to reduce future complexity.
The strict exclusion of external web font downloads to minimize bandwidth usage and maximize rendering speed.
A Google Sheet template provided to the client to securely share credentials for domain registrars, hosting, and payment accounts.
The formal point, 48 hours after handover, where the laboratory’s responsibility for system performance and errors permanently ends.
A specific headline style (H1) using tight line-heights (1.07–1.14) to create a high-impact, “machined” look.
A hard performance limit requiring a single-page website to remain under 1MB in total size.
A discovery phase procedure used to identify a business’s specific competitive edge over its rivals.
The visual mapping of the specific steps a visitor takes to complete a primary goal on the website.
A content strategy where text is written as reusable modular blocks to ensure consistency across different platforms.
A global CSS system that prevents inline style overrides to maintain design discipline.
A quality audit ensuring that design elements (size, color, weight) guide the user’s eye toward the most important business information first.
The set of defined CSS variables (e.g., #1b5e20 for Green Deep) used to maintain absolute visual consistency across the system.
A technical requirement for the final HTML/CSS code to pass formal validation tests without errors.
A technical requirement for the final system code to pass official web standards tests without errors or warnings.
The technical requirement to use modern, high-compression image formats to maintain visual quality while reducing file size.
A minimalist structural approach that uses spacing alone to guide user focus without visual clutter.
A strategic decision to avoid database-driven platforms like WordPress to eliminate security vulnerabilities and maintenance.
A coding standard that rejects heavy frameworks (like Tailwind/Bootstrap) in favor of semantic HTML5 and frozen CSS.
A design state where the client is never restricted or locked out of their own accounts by the developer.
A system design that ensures the client is not locked into or reliant on a specific developer or platform.
A system design standard ensuring that a client is never restricted from moving their website or changing developers.