Orientation
Orientation
Giving someone the CAD files and circuit schematics for a commercial product is useless if their digital files are a wasteland, their physical workspace is chaotic, and they don't know how to document their supply chain.
If you are here simply to build a cool switch in your garage on a weekend, you can skip directly to the Engineering Labs. But if your goal is to turn technical knowledge into a scalable product, an independent business, or a lifelong trade, you must build your support infrastructure first.
The Postern Press relies on a strict four-part organizational and operational foundation. Do not attempt to scale a business or launch a product without first establishing this baseline.
The physical layout required to process information efficiently. You cannot execute high-level technical work on a cluttered kitchen table or a single 13-inch laptop screen. The "Cockpit" is the non-negotiable physical environment required for deep work.
The Hardware: Specific requirements for chairs, desks, computers, multi-monitor arrays, printers, and scanners.
The Layout: How to position tools for rapid information processing.
Access the Module: [Link to your BRICS Practice Management Cockpit Page]
The physical mechanics of a clear workspace. Even in a digital world, physical components, receipts, test boards, and printed schematics will bury you if you lack a routing system.
The Supply Chain of the Desk: Required office supplies, inbox/outbox mechanics, and hard-storage systems.
Access the Module: [Link to your BRICS Storage/Organization Page]
Why Microsoft Word and a consumer Gmail account will not scale. The modern independent builder must operate as a highly efficient, multi-account database. We utilize Google Workspace—not as a corporate HR tool, but as a lean, rapid-deployment file system.
Configuration: How to set up Google Workspace for a 1-to-3 person solo-enterprise.
Drive Mechanics: Desktop syncing, cross-account file management, and directory structures.
Access the Module: [Link to your 220 Club Workspace Guide]
Your personal knowledge base and public publishing tool. If you cannot organize your thoughts and present your ideas, your technical skills do not matter. We use Google Sites as the primary engine for internal documentation and external publishing. It is the fastest, most resilient, and lowest-cost way to build a digital brain.
Building the Engine: How to use Google Sites as a personal wiki and operational manual.
Access the Module: [Link to your 220 Club Google Sites Guide]
The Postern Press curriculum is age-agnostic, but the pacing must be adapted to the student's background. If you are an educator, a parent, or navigating your own career transition, use the following guide to consume this material.
For the Ex-Corporate Professional (Ages 30–60+) You likely possess deep organizational understanding, but you are accustomed to bloated corporate support systems. Your challenge is unlearning the bloat and scaling down to the micro-level. You can consume the Core Infrastructure modules in a weekend. Treat it as a rapid recalibration, then move immediately into the engineering projects to see how the micro-framework applies to product development.
For Young Adults (Ages 18–25) Do not confuse smartphone proficiency with operational competence. You have energy, but you likely lack both real-world business organization and deep technical skills. Do not skip the Core Infrastructure. You must force yourself to build your Physical Cockpit and your Google Sites documentation hub before you touch a CAD program or a soldering iron.
For Youth & K-12 Students (Ages 10–18) This is a multi-year curriculum. Mentors should spend an entire semester helping the student build their Physical Cockpit and master Google Drive organization. Teach them that documenting a process in Google Sites is just as important as the physical build. Once they prove they can organize their thoughts and files, they will be ready to tackle the Current Sensing Switch and beyond.
For your Google Sites top-navigation menu, I recommend this clean, sequential layout:
The Manifesto (Home Page)
Core Infrastructure (This page—acting as the bridge/prerequisite)
The Colleges (Dropdown Menu)
College of Applied Mechanics (Leads to the Switch, Bandsaw, etc.)
College of Independent Commerce (Coming Soon - points to BRICS/Biz docs)
College of Clinical Systems (Coming Soon)
Catalog / Access (Where people buy the licenses / paywall info)
How does this structural map feel to you? Once you paste this in and link it up, your users will have a crystal-clear path from "total beginner with a messy desk" to "ready to build industrial hardware."