White Noise Academy:
An Induction Docket for Fresh Engineers

The mission

We turn fresh engineers into founders: one loop a day, every solution ending in hardware and a customer, shipped in public at AI speed.

Every clause carries weight. Fresh engineers because that is who we take and who we are best at growing. Founders because the outcome is ownership, not employment: a person who can find a customer, build the solution, ship it, tell its story and sell it, and who has done so in public where the record cannot be disputed. One loop a day because the unit of progress is the daily cycle from theory to bench to code to broadcast, and a day without a shipped artifact is not a day of work. Hardware and a customer because a solution that can be held and a person who paid for it are the two things that cannot be faked. In public because trust is built by being watched. At AI speed because velocity is the name of the game, and the tools now make a pace possible that was unthinkable two years ago.

The vision

We see an Academy that is also a company, where teaching and shipping are the same activity, filmed once and sold forever. We see instruments, not apps, leaving our bench and entering people's hands. We see small, sovereign models that speak the languages the large laboratories ignore. We see a channel whose viewers become patrons, whose patrons become customers, and whose customers become the next cohort's first assignments. We see graduates who lead verticals and recruit their own teams from the hundreds who applied and were not yet selected. And we see the whole of it written down, so that another college in another state can run the same playbook.

The family

An organisation is not an organisation chart. It is an organism, and it grows by addition. We describe the family as concentric circles, each with its own way in and its own obligations under this docket.

The circles are not ranks. A patron who becomes a customer, a contributor who joins a cohort, a graduate who returns as core team: the movement between circles is the health of the organism, and the docket is written so that movement is always possible and always earned.

The Academy did not begin with engineering. White Noise Academy began in Hyderabad as a place where children learned music, arts and film production seriously, with graded certification from the Rockschool examinations board in London, and it grew into a school of holistic education: a full-time homeschooling programme, an after-school Root Skills programme for younger learners, and the Whitenoise Teen Accelerator Program, which describes itself as India's first holistic teen accelerator and combines AI-driven education with real-world projects across eighteen career tracks and a nine-step learning framework. The Root Skills programme organises its work into three modules that still describe us well: technology innovators, creative visionaries, and digital storytellers.

That history is why this docket reads the way it does. We treat an engineer the way a music school treats a musician: daily practice, graded gates, public performance, and a portfolio rather than a certificate. We treat a product the way a film school treats a film: it is not finished until it has been shown to an audience. And we treat a classroom the way a studio treats a session: it is recorded, and the recording is the product.

The engineering practice came through a partnership with dKube and One Convergence, whose forward-deployed engineering training defined the genome method that Part III adopts: an engineer is not a label but a cell, expressing whatever faculty the field demands. The training's operating loop of understand, formulate, optimise and ship, its gates, and its rule of manifestation over certification are all carried into this docket with attribution.

Faculty and mentors, as published

The Academy's public faculty, as listed on its programme sites, are Dr Shruti Arya, Curriculum Director; Anuradha K, Mathematics; Krithika, Creative Arts; Sagar Gaikwad, Music, Curriculum and Production; and Haritha H, Primary Years inquiry faculty. Its published industry mentors are Vinai Kolli, embedded systems, Vice President at DKube, with more than thirty years in the field; Lata Murkot Ramuny, sales leadership at the Taj and Tata groups; Sunila Gollapudi, a Director at Google; Girish Marar, artist and sculptor, founder of Greekbay; and Bhupesh Kumar, systems design at Verizon and Wells Fargo. These names are recorded here as the Academy publishes them, so that a new engineer knows whose shoulders the programme stands on. The core team that carries a cohort day to day is described by role in the next section, and its names are added to each cohort's edition of this docket before printing.

The Academy is based on the sixth floor of Brigade Towers in the Financial District, Gachibowli, Hyderabad. Cohort 1 of the engineering programme is hosted at GIET in Gunupur, Odisha, from where the first engineers were selected through the Code Arena assessment.

Every cohort is carried by an experienced core team of eight. The number is not incidental. It matches the eight stages of the lifecycle in Section 16, so that every stage has a person who has done it in production and can be called to the bench. The roles are fixed; the names are added per cohort.

Mentorship works in three modes. Scheduled: each role owns a block of the Loop and is present for it. On call: during Forward Deployment any engineer may summon any mentor to the bench, and the mentor comes; the rule is that a mentor never solves the problem, they ask the question that lets the engineer solve it. Gated: at each of the four gates in the lifecycle, a mentor of the relevant stage signs that the exit criterion is met, and the signature is recorded on the radar. The core team also sits as the council described in Section 29.

The mentors are bound by this docket exactly as the engineers are, and by three further undertakings: to teach in public, so that their sessions are recorded and become the members' curriculum; to score on evidence only, never on impression; and to escalate a health or conduct concern the same day they notice it.

Instruments, not apps

Every solution the Academy ships ends in hardware, however small. A device you can hold, with knobs and sliders that look and feel like a mixer or a piece of studio gear, and a digital brain inside: a small language model, an agent, a bridge into the legacy systems that run real factories and laboratories, such as LabVIEW, Verilog and the industrial buses. The user interface behaves like a digital audio workstation or a plug-in, with physical controls that map to real parameters, and beneath it the integration goes as deep as the customer's oldest equipment. This is the opposite of a white box with three buttons that opens a chat window. An instrument is built for one domain, does one job extremely well, and is beautiful in the way that tools people use every day become beautiful.

We say instruments, not apps, because the phrase decides what we will not do. We will not ship a web page and call it a product. We will not ship a chat window and call it intelligence. We will not ship a generic device and call it a solution. The product line, and the product identity inside the Academy that carries the Foundry name, is a line of instruments, and the software is what makes them think.

Two product lines

Line 1: domain small language models. Narrow, owned, and trained on data nobody else has: Odia and the other languages the large laboratories ignore, agriculture, the clinic, the college itself. A small model that does one task in one language for one kind of customer beats a large model that does everything for no one in particular, and it can run on a device the customer owns. This line sells to organisations that want their own model and cannot get one from a laboratory in another country. The fine-tuning platform that produces them already exists in the practice.

Line 2: the fab and custom-instrument line. We do not invent new boards. We take a customer's need and turn it into a kit, a printed enclosure, an ordered circuit board bundled with an ESP32 or an Arduino, or a custom design workshop in which the customer builds it with us. This line grows by customers outsourcing their small hardware needs to us, and by collaborations that make noise. Over time it becomes the body for Line 1's brain.

The channel as the front door

Both lines share one front door: the channel, and the hundred patrons who follow the process live. We are not chasing a million viewers who watch for fun. We are earning a hundred people who trust us because they watched us build, who back the process, and who become the first customers of the custom work. The way to earn them is to show, on camera, that the fears about AI collapse once the process, the skills and the agentic frameworks are built from the ground up, and that velocity follows. The channel, its lanes and its membership are described in Section 21.

What we make is recognisable before the logo is seen. This section states the design philosophy behind every Academy product, so that an engineer in week one already knows what an Academy instrument must feel like and what it must never be.

Voice first

The first way to use an Academy product is to speak to it. A person says what they intend, the system reasons and acts, and it narrates back what it started, what it finished and what went wrong, without the person having to watch a screen. This is not a novelty layer on top of a keyboard product. It is the accessibility layer: eyes-free, hands-free, and approachable by a person who has never used a terminal and never will. The terminal remains the power-user surface. Voice is the surface that needs no terminal at all. Every product is judged against one question: does it let a person do by voice what they would otherwise do by typing? The consequences are a reliable voice loop, proactive narration, continuity across sessions because there is no scrollback to read, and support for the languages our customers actually speak.

The analogue board

The second way to use an Academy product is to touch it. Where a product has parameters, it has physical controls: knobs with detents, faders, switches, meters and small displays, laid out the way a mixing console or a studio effects unit is laid out, because that idiom has survived sixty years of use by people under pressure. The digital audio workstation and the virtual studio technology plug-in taught a generation that a parameter can be a knob on a screen. We complete the circle and put the knob back in the hand, mapped one to one to the same parameter, with the on-screen replica showing exactly what the board shows. A small analogue-looking device with a digital brain inside is more trusted, more understood and more loved than a black box with three buttons, and it can be operated without looking.

Old-school interfacing

Beneath the board is a discipline that predates the web. We read the datasheet before we reach for a library. We know the register map. We speak the buses, serial, I2C, SPI, CAN and Modbus, with a probe on the wire, and we bridge into the systems that run real laboratories and factories: LabVIEW, Verilog on programmable logic, ladder logic on controllers, and the serial protocols of instruments older than the engineers using them. A product that cannot talk to the customer's oldest equipment is not deployed; it is demonstrated. Multi-bus communication, a legacy bridge and deterministic timing are core skills of the curriculum for this reason, and the bench and silicon lead signs the hardware gate on them.

Design language

Typography is set in faces that were designed for reading, on paper and on panels, and the same faces appear in our documents, our screens and our printed scales. Colour is used to mean something, never to decorate: a meter in the red is a warning, a knob ring in a colour is a mode. Panels are laid out in the order the operator uses them, left to right, top to bottom, with the most-turned control largest and nearest the hand. Enclosures are metal where metal can be used, with printed inserts where a shape demands it. Every instrument must be understandable by someone who has never seen a screen, and every screen must be understandable by someone who has never seen the instrument.

The ethics of the Academy are short because they are absolute. They apply to engineers, mentors, contributors and partners alike, and to the things we build as much as to the way we behave.

Honest results

We never fabricate a result, a benchmark, a test outcome, a user number or a customer quote. A number that appears in a video, a handout, a betadoc or a report was measured, and the measurement can be reproduced from the artifacts we publish. When a benchmark is unfavourable to us, it is published with the same prominence as one that is favourable. When a demonstration is staged for the camera, the staging is disclosed on screen.

Attribution

We credit the people, papers, repositories and models we build on, by name, in the artifact itself. Work generated with AI assistance is disclosed as such where a reader would reasonably want to know, and the human who verified it is named as responsible for it. We do not present a reproduction as an invention.

Consent

No person appears on camera, in a transcript, in a dataset or in a case study without informed written consent, and consent is specific: it says what is recorded, where it will be published, and how it can be withdrawn. A customer's employees, a clinic's patients and a farmer's family are not "the customer" and their consent is separate. Consent obtained under pressure is not consent.

Data minimisation and the PII rule

Personal data is treated as radioactive by default. We collect the minimum a solution needs, keep it for the minimum time, and prove that personally identifiable information is redacted before any external call is made. Client data is never used to train a model without written consent for that purpose. Where a solution can run on a device the customer owns, it does, and the data never leaves.

Hardware in people's hands

An instrument we ship can burn, shock, or fail in a way that harms. Every device that leaves the bench has been tested for electrical safety, thermal behaviour and mechanical failure, and the test is recorded. Lithium cells are protected. Mains voltage is never exposed. A device intended for a child meets the applicable standards before it is sold, not after.

What we will not build

We do not build systems whose purpose is to deceive people, to surveil them without their knowledge, to discriminate against them, to harm them, or to evade a law that protects them. We do not build a thing for a customer that we would refuse to publish. When an engineer is asked to build such a thing, they refuse and report it, and the refusal is protected.

This code applies to everyone in every circle of the family, in the building, on the bench, on the channel, in the repositories, in chat, and at any event where the Academy is represented. It is enforced by the People and HR lead and the council, and acknowledging it is a condition of joining.

Respect

We treat every person as capable of learning, as deserving of a straight answer, and as entitled to their dignity. We criticise work, not people. We ask before we assume. We listen to the quietest person in the room before the loudest, because the quietest is usually the one with the observation nobody else made.

No discrimination

The Academy does not discriminate, in selection, assignment, assessment, reward, growth or treatment, on the basis of gender, gender identity, sexual orientation, caste, religion, language, region, ethnicity, disability, age, marital status, family responsibility, economic background or the college a person came from. This is a rule, not an aspiration, and a breach of it is a breach of the docket.

Equal opportunity

Every engineer in a cohort has the same access to mentors, bench time, tools, customers, camera time and the radar. Assignment to a vertical, to a customer or to a lane is made from the radar's evidence and the engineer's stated interest, and the reasoning is written down. Where two people are equally placed, the tie is broken by a stated rule, never by a preference. Reward and growth are performance-based, as Section 25 states, and performance is measured by evidence that every engineer can see for themselves.

Harassment

Harassment is any unwelcome conduct, verbal, physical, visual or online, that demeans, intimidates or threatens a person, or that makes their participation in the Academy conditional on tolerating it. It includes sexual harassment as defined by the law of India, and it includes the subtler forms: exclusion from information, repeated interruption, mockery of accent or background, and the assignment of menial work along the lines listed in the non-discrimination rule. Harassment is grounds for removal from the family.

The reporting path

A person who experiences or witnesses a breach of this code may report it to the People and HR lead or to any member of the core team, in person, in writing or through the confidential channel named at induction. A report is acknowledged within one working day and investigated by two members of the council who are not the subject of it. The person who reported is protected from retaliation absolutely; retaliation is itself a breach and is treated as the more serious one. The outcome is communicated to the reporter. Where the law requires an internal committee, the Academy constitutes one and this path feeds it.

Communication norms

We write in the open by default, in threads that others can search. We disagree in public and decide in public, and once a decision is made we carry it out as if it were our own. We do not send a message after the Wednesday stop or on a day off that expects a reply before the next working day. We say "I do not know" and "I was wrong" without ceremony, because the alternative is a culture in which nobody learns.

Conflict resolution

Disagreement about work is resolved on the evidence, by the two people involved, within the day if possible. Disagreement that persists goes to the mentor of the relevant stage. Disagreement about a person goes to the People and HR lead through the reporting path. Disagreement about this docket goes to the council through the amendment process. Nobody is ever asked to resolve a conflict with someone who holds power over their reward.

Consequences

A first breach of a conduct rule, other than harassment or discrimination, is met with a conversation and a written note. A second is met with a warning recorded on the radar. A third, or any breach of the harassment or discrimination rules, is grounds for removal from the cohort and the family. Removal is decided by the council with the People and HR lead, and the person is heard before the decision.

Indian law, under the Sexual Harassment of Women at Workplace (Prevention, Prohibition and Redressal) Act, 2013, requires an employer with ten or more people to constitute an Internal Committee. The Academy constitutes one for every location where it works, including a hosted cohort, and this section states how it is reached and how it acts. The code of conduct's reporting path feeds it; it does not replace it.

Composition

The committee is chaired by a senior woman member of the core team, includes at least two further members of the family committed to the cause of women or with legal or social-work knowledge, and includes one external member from a non-governmental organisation or a person familiar with the issues of sexual harassment. At least half the members are women. The names and contact details of the members are displayed by the bench and on the members' page of the Academy site, and are entered in each cohort's edition of this docket before printing.

Making a complaint

A complaint is made in writing to any member of the committee within three months of the incident, or of the last incident in a series; the committee may extend this period for reasons it records. A person who cannot write is helped to. The committee may, at the request of the aggrieved person, attempt conciliation before inquiry, but never a monetary settlement as the basis of conciliation. The inquiry is completed within ninety days, both sides are heard, and a report is given to the employer within ten days of completion. The employer acts on the report within sixty days.

Protection and confidentiality

The identity of the complainant, the respondent, the witnesses, and the contents of the complaint and the inquiry are confidential, and publishing them is itself a breach. During the inquiry the committee may recommend that the complainant or the respondent be transferred, given leave, or otherwise relieved so that they need not work together. Retaliation against a complainant or a witness is treated as the more serious breach, as Section 9 states. A false complaint made with malicious intent is also an offence, but a complaint that is not proved is not thereby malicious.

Reporting wrongdoing

Any member of the family who reasonably believes that a law, this docket, or a customer's trust is being broken, whether by an engineer, a mentor, a partner or the Academy itself, may report it to the People and HR lead, to any member of the council, or, where those are implicated, to the external member of the Internal Committee. A report may be made anonymously. The person reporting is protected from any adverse consequence, and a report made in good faith that proves unfounded is not held against them. The council records every report and its outcome in the memory document, with identities removed.

Gifts, hospitality and conflicts

We do not give or accept anything of value to obtain or keep business. A gift or hospitality above a modest value, set by the council and published, is declined or declared to the People and HR lead, who keeps a register. Meals shared with a customer during a field deployment are normal and are recorded as expenses. A gift from a supplier that might influence a purchasing decision is always declined. Conflicts of interest are declared under Section 12 before work begins.

Bribes and facilitation payments

The Academy makes no facilitation payments, to any official or intermediary, for any permit, licence, clearance, connection or approval, however small and however customary. An engineer asked for one refuses, records the request, and reports it the same day. The Academy will lose the permit rather than pay. Where a payment is demanded under threat to a person's safety, the person pays and reports immediately, and the Academy treats it as extortion, not bribery.

Books and records

Every payment the Academy makes or receives is recorded accurately, with what it was for, and every expense an engineer claims has a receipt. No account is kept off the books, and no description is written to disguise a payment's purpose.

Non-disclosure

Every person in the engineer, core-team and partner circles signs the non-disclosure acknowledgment in Appendix E. It covers customer and patient data, a customer's unpublished deliverables and business information, credentials and keys, unpublished product plans that the council has marked confidential, and the personal information of other members of the family. It does not cover anything the Academy publishes, which is almost everything, and it does not cover a person's own skills, which they take with them. The obligation survives the engagement by two years.

Public by default, and the exceptions

The Academy publishes its code, its documentation, its process, its curriculum, its schedule, its live dashboard, its recorded sessions and its builds. Five things are never public.

• Customer and patient data. Names, records, footage and any derived dataset, without written consent for that specific use.
• Individual radar scores. A person's eight-axis profile is visible to that person and to the core team only. Team totals and shipped work are public.
• Health records. Check-in notes stay with the physician and physiotherapist. Only "cleared" or "rest day" reaches the schedule.
• Keys, secrets and credentials. Stored in the designated keys file, never in a repository, a chat or a recording.
• Per-piece opt-outs. Any person may opt out of any single recording or publication by saying so before it is cut, and the opt-out is honoured without question.

Intellectual property

Work produced for the Academy's own products, curriculum and channel is owned by the Academy and published under the Apache 2.0 licence, with the author credited in the artifact. Work produced for a customer under a customer agreement is the customer's exclusive property, including the outputs derived from the customer's information, and the Academy retains only the right to describe the engagement in general terms with the customer's consent. A model trained on a customer's data belongs to the customer. Contributions from the contributor circle are accepted under the same licence, and a contributor keeps their copyright.

Conflicts of interest and outside work

A member of the family declares any interest in a customer, a supplier, a competitor or a partner before working on anything that touches it. Outside work is permitted if it is declared, does not use the Academy's customers, data or confidential information, and does not compete with a product the Academy is building. When in doubt, declare it; the People and HR lead keeps the register.

Integrity

We do what we said we would do, and when we cannot, we say so before the deadline rather than after it. We do not represent another person's work as our own. We do not use the Academy's name, channel or customers for personal gain without the council's agreement. We keep the promises in this docket to each other even when nobody is watching, which is the only meaning of the word.

The Academy's day is long and its bench is dangerous, and we have a physician and a physiotherapist on the core team precisely because most engineering programmes do not. The health rules are enforced by them, not by an engineer's willpower, and they outrank every deadline.

Hours and rest

The Loop runs from nine in the morning to eight in the evening, a ten-hour working day plus lunch away from the desk, Monday to Saturday during the internship. Attendance is recorded by the biometric at the start and the end of the day, as Section 26 states. Wednesday stops at half past five for everyone, without exception, and nothing is scheduled after it. Sunday is fully off: no chat, no commits, no calls; the music club on Sunday morning is voluntary and is not work. A mentor who schedules work into the rest day has breached this docket. Once permanent, the minimum is nine hours per working day.

The weekly check-in

Once a week the Voice hour becomes a check-in with the physician and the physiotherapist. It is mandatory, it is private, and it is the place where fatigue, pain, sleep, mood and anything else are discussed. The physician may declare a rest day for any engineer, and the rest day is honoured without explanation to anyone else. Only "cleared" or "rest day" reaches the schedule.

Bench and laboratory safety

Soldering is done with extraction and eye protection. Mains voltage is never worked on live and never exposed on a bench where others sit. Lithium cells are stored in a fire-safe container, charged under observation, and never punctured, shorted or left connected overnight. The 3D printer runs with ventilation and is not left unattended for long prints. Static-sensitive parts are handled on an earthed mat. Every injury, however small, and every near miss is recorded the same day. The bench and silicon lead can stop any activity on the bench at any time, and the checklist in Appendix G is signed by every engineer before the first bench session.

Mental health

A twelve-hour day of learning and shipping, in public, with a radar that scores you every week, is a load, and it is normal to find it heavy. Saying so is not weakness and is never scored. The physician is the first person to speak to; the communication coach and the People and HR lead are also available; and a referral to an external counsellor is arranged by the physician on request, at the Academy's cost, in confidence.

Escalation

A health or safety concern about oneself or another person is raised the same day to the physician, the physiotherapist or the bench lead. A concern that the rules are being bent, for instance a pattern of late-night messages, is raised to the People and HR lead through the reporting path in Section 9. An emergency is handled by the emergency services first and the Academy second; the numbers are on the wall by the bench.

Every engineer works with AI beside them all day, and the Academy's own machine is built of models. This section states how the tools are used, so that speed never costs a customer their data or the Academy its honesty.

What may be sent where

Models are classed by where they run and who operates them. A local model on the Academy's or the customer's machine may see anything the engineer may see. A model operated by a provider under the Academy's paid seat, with contractual no-training terms, may see code, documentation and synthetic or public data, and may see customer data only after the redaction gate has removed personal information and the customer's agreement permits external processing. A free or consumer model, or any model without such terms, sees nothing that belongs to a customer and nothing marked confidential. Keys and secrets are never sent to any model. When in doubt, the local council of models is used, or the forward-deployment lead is asked.

The redaction gate

Every external call from a solution passes a gate that detects and redacts personally identifiable information, and the gate's log is an audit receipt. The gate is not optional, it is not disabled for a demonstration, and a solution without it does not pass the Governed gate. Engineers are taught to treat personal data as radioactive: it is handled with the shortest exposure, by the fewest people, and it leaves no trace where it is not needed.

Prompt and context hygiene

A prompt is code. It is versioned, reviewed and tested like code, and a prompt library is an artifact of the curriculum. Context given to a model is the minimum it needs for the task, never a whole repository or a whole database because it was easier. Agents are given typed tools rather than free rein, so that they act rather than guess, and every state-changing action an agent takes is logged as a receipt.

Verification and responsibility

A model's output is never a source of record. Every artifact a model produces that reaches a customer, a repository, the channel or a decision has a named human who verified it, and where the finding matters, a council of models of different families has agreed on it. An engineer who ships an unverified model output is responsible for it exactly as if they had written it, because they did.

Disclosure

Work produced with AI assistance is disclosed as such wherever a reader would reasonably want to know: in a commit that is largely generated, in a piece on the channel, in a document given to a customer. Disclosure is a line, not an apology. The Academy's position is that AI-assisted work verified by a competent engineer is simply engineering, and that hiding the assistance would be the dishonest act.

The seat

Each engineer's AI seat is provided by the Academy under Section 22, is used for Academy and cohort work, and is tied to the engineer's Academy email. It is not shared, its usage is visible to the engineer and the training lead, and it is returned on leaving.

Identity

Every engineer is issued an Academy email address at whitenoiseacademy.com, and uses it, and no other, for every work-related and social account, subscription and service used in the course of the engagement: the AI seat, the source-code host, the cloud console, the channel tools, the members area, and any subscription the Academy pays for. Two-factor sign-in is enabled on every account that offers it, a password manager holds every credential, and no password is reused. Access cards and fingerprint identities are issued at induction; the card opens the building and the lockers, and the biometric records attendance as Section 26 describes.

Devices

The Linux workstation is the Academy's and is encrypted at rest with a screen lock of at most five minutes. Personal laptops may be used for reading and for the channel, never for customer data. Personal phones never hold customer data, customer contacts or customer conversations. The work phone, issued under Section 22, is the only device used for customer interaction; it stays in the engineer's locker outside working hours and does not leave the building. A lost or stolen device is reported within the hour to the People and HR lead, who revokes its sessions.

Network and secrets

Solutions and machines join the private mesh with an identity of their own; nothing is exposed to the public internet except through the demonstration gateway, time-boxed. Secrets live in the designated keys file and in the runtime secret store, never in a repository, a chat, a screenshot or a recording; a secret that has been seen on screen is rotated the same day. Public wireless networks are used only through the mesh.

Phishing and social engineering

Nobody at the Academy will ever ask for a password, a one-time code or a key by message or by phone. A request that seems to come from a mentor, a customer or the council and asks for credentials, a payment or an urgent exception is reported, not answered. The most convincing message is the one to check.

Incidents

A suspected breach, a leaked key, a device lost, a customer's data exposed, or an agent that did something it should not, is reported the same hour to the forward-deployment lead and the People and HR lead. The first step is containment, the second is the customer told the truth, the third is the record written, and the fourth is the fix. Nobody is blamed for reporting; people are blamed for hiding.

Every day follows one unbroken cycle. A concept in the morning, its physical application before lunch, the code that consumes it in the afternoon, and an articulation of the whole before the day ends. The order matters: because the broadcast requires you to explain what you built, the concept is locked into memory before you leave the room. The Loop is printed on one page in Appendix A and lives at the schedule page of the Academy site.

The six-beat lesson

Every taught topic, in First Principles and in the Vertical Hour, follows the same six beats, borrowed from the forward-deployed engineering curriculum: Motto, the one sentence to remember; Problem, the real situation the topic solves; Concept, the idea from first principles; Build it, the artifact made in the session; Use it, the artifact applied to something real; Ship it, the artifact committed or recorded. A lesson runs forty to forty-five minutes and produces one concrete thing: a checklist, a brief, a model, a matrix, a schematic, a specification, a repository, a prompt library or a skill. A lesson that produces nothing was a talk, and we do not give talks.

The week

Monday's Open is cycle planning: every engineer names this cycle's customer and artifact, and the health check-in replaces Voice. Tuesday is the standard Loop. Wednesday is the standard Loop until the hard stop at half past five; the broadcast is a written note only. Thursday is the standard Loop, and the content team publishes the week's long-form pieces from the footage so far. Friday afternoon is Demo and Radar Review: every engineer demonstrates live, mentors score all eight stages, and the radar is updated for the week; at five the Live Build show goes on air, a caller's application built and delivered in thirty minutes, with engineers rotating as crew. Saturday is a standard Loop day, the sixth of the internship week. Sunday is off, fully, and the music rooms are open from ten until one for anyone who wants them.

The sixteen weeks

A cohort runs sixteen weeks in four phases. Bootcamp, weeks one and two: the toolchain, the pipeline, the bench, the rules; project zero is the radar tracker itself, built by the engineers who will be measured on it; every engineer ships one tiny solution end to end and finds a customer. Sampling, weeks three to eight: the Vertical Hour rotates through the eight stages one week at a time, so that everyone has touched all eight with real work; two small solutions per engineer, each with a named customer in the college or the town; the radar profile forms from evidence; the first patrons follow live. Lock-in, weeks nine to twelve: the vertical is chosen with the radar; solutions move onto the two product lines; prototypes go into customers' hands; custom design workshops open. Ship, weeks thirteen to sixteen: the pre-order batch, the betadocs, the public launch, demo day; confirmation, and vertical leads named. The week-by-week curriculum across the four tracks is in Appendix B.

The four tracks

The curriculum runs four tracks in parallel, one per block of the day. First Principles covers the mathematics of signals and probability, digital design from gates to buses, analogue and digital electronics, and system architecture from a single process to a mesh. The Bench covers measurement, breadboarding, schematic capture, board layout, enclosure design, printing and assembly. Code and models follows the forward-deployed engineering lesson spine: version control, models and prompting, local versus cloud with the PII gate, skills and pipelines, schema and contract design, agentic planning, tool servers, context-engineered pipelines, task-specific model selection and small tuning, server-rendered services, mixture of cloud, cost routing, privacy and residency, threat modelling, mesh and access control, observability, verification, consensus, testing across dimensions, audit receipts, deployment, marketing, community and support automation; on our bench it adds firmware, edge runtimes and on-device inference. Voice covers speaking, writing, the pitch, the interview, the demonstration and listening.

The Academy began as a school of music, arts and film, and it keeps that inheritance deliberately. An engineer who can only engineer cannot tell the story of what they built, cannot cut the film that sells it, and cannot rest in a way that restores them. The creative skills below are part of the programme, not an extra.

Scripting and storytelling

Every piece on the channel begins as a script, and every script begins with the same question the communication coach asks in the Voice hour: what does the viewer know at the end that they did not know at the start? Engineers learn to write a hook, a build, a result and a close; to structure a ninety-second short and a twenty-minute long-form; to narrate a failure so that it teaches; and to write the one-page handout that turns a viewer into a member. The scripts are artifacts, committed alongside the code they describe.

Video editing and filmmaking

The content team produces the long-form pieces, but every engineer learns to shoot and cut. Framing a bench shot, recording clean audio, screen capture that a viewer can read, a cut that keeps the pace, colour that matches between the camera and the screen, and the narrated demonstration film that every betadoc carries. By the end of the cohort each engineer has cut their own short pieces for weeks and has crewed the live build show. Filmmaking is taught the way the Academy has always taught it: on real projects, for real audiences, with the film shown.

Illustration, sound and design

The morning lesson becomes a diagram; the diagram becomes the members' handout. Engineers learn to draw a system so that a stranger understands it, to design a panel and a scale, to choose a typeface for a reason, and to make a sound for a device that tells the operator what happened without a screen. These are the same skills the Root Skills programme teaches its younger learners as creative visionaries and digital storytellers, taught here at working depth.

The music club

Every Sunday morning from ten until one the Academy's music rooms are open to every member of the family, free of charge. The club is voluntary, it is not work, and no work is discussed there. Anyone may learn an instrument from the beginning, play with others, or follow the graded Rockschool progression that the Academy has offered its music students for years, with grading available to any engineer who wants it. The club exists for mental peace and balance: after a week of building, an hour of playing is one of the ways we rest, and it costs nothing on the radar to come or to stay away. Sunday remains a day off; the club is one of the things a day off is for.

The genome method

Every cell in a body carries the same genetic material; what differs is which genes are expressed. We take the same view of an engineer. An engineer is not a label. An engineer is a cell that carries one engineering genome and expresses whatever faculty the problem in front of them demands: front end today, firmware tomorrow, security reviewer on Friday, agent orchestrator next week. We therefore do not certify "a front-end person" or "a data person". We grow people who can differentiate quickly, and we measure the latency of that differentiation rather than the depth in any one layer.

Three practices follow. Learning how to learn is the central gene: to decompose an unfamiliar intent into checkable claims, to delegate the mechanical work to agents, to verify adversarially, and to internalise the pattern so that the next differentiation is faster. If we taught a fixed stack, the programme would expire with the stack. Express while you update: a cell does not stop functioning to grow, and neither do we; the deliverable ships while the domain model is refined in the same loop, and learning is harvested from output rather than scheduled instead of it. Altitude control: beyond the horizontal axis of scope and the vertical axis of the lifecycle, a forward-deployed engineer moves deliberately along a third axis, from the architecture diagram to a single failing log line and back, without changing tools.

Paradigm fluency

Programming paradigms are genes to express, not ideologies to defend. Agentic when the work exceeds one person's hand. Parallel when sub-tasks are independent and speed matters. Functional when correctness and testability dominate. Sequential when a clear chain is clearer than an abstraction. Imperative when control over hardware or performance is the point. In the Vertical Hour, an engineer is regularly asked to solve the same problem twice in two paradigms and to defend the switch.

The named-customer rule

No solution is designed until it has a customer with a name, a problem and a reason to care, and that customer has said so on record. "Innovative solution" is not a customer. "Small businesses" is not a customer. The owner of the pharmacy on the main road, who loses an hour a day to a stock ledger, is a customer. In Bootcamp every engineer goes into the college and the town and comes back with one. On the Friday of week two, every engineer pitches; the council chooses the first two solutions to carry onto the product lines, one from each line, and the rest become sampling projects.

Sitting with the customer

Forward deployment means the engineer goes to where the problem is. They sit in the clinic, stand in the field, watch the ledger being written. They install the first version themselves, watch it being used, and fix what they see in the same visit. The customer's word at each gate is evidence on the radar. A solution the engineer has never watched being used has not been verified, whatever the tests say.

The radar is how work is measured, how verticals are assigned, and how autonomy is earned. It is built from evidence, not opinion, and every engineer can see their own profile at any time.

The eight axes

Every solution an engineer ships is scored on all eight stages of the lifecycle, from the artifact that stage produced: the customer's recorded word for Discover, the specification for Design, the running repository for the software build, the powered device for the hardware build, the test results and consensus verdicts for Verify, the live deployment for Ship, the published piece for Tell, and the order or the reasoned refusal for Sell. Scores are given at the Friday review by the mentor of each stage, on a five-point scale with a written reason, and the engineer sees the reason.

Interest, aptitude, velocity

Over a cohort the radar accumulates three things per engineer. Interest: which stages they chose to spend their Vertical Hour and their sampling projects on. Aptitude: which stages scored well, on the evidence. Velocity: how long each stage took, from gate to gate. By the end of Sampling the three together say, to the engineer and to the council, which vertical they should lead, and the choice is made by both. Where interest and aptitude disagree, the engineer is told plainly and the choice is theirs, with the evidence in front of them.

Who sees what

Team totals, shipped work, and the live dashboard are public. An individual's eight-axis profile and the written reasons are visible to that engineer and to the core team only. Health notes never touch the radar. A conduct warning is recorded on the radar as a dated note, visible to the same people.

Manifestation, not certification

The Academy does not issue certificates. It issues a manifestation portfolio: the deployed artifacts of a cohort, each with its audit receipts, its consensus verdicts, its test results and its customer's word, presented as a phasedoc cockpit that a reviewer clicks rather than reads, and a betadoc that a customer can be shown. Manifestation is evidence that a person built and shipped a governed solution. A credential earned this way renews itself from continued shipping: an engineer who keeps shipping keeps their level.

Autonomy levels

The channel is the Academy's first product. It is how the hundred patrons find us, how members join, how customers reach us, and how the next cohort is recruited. Every session of the Loop is recorded, every build is filmed, and the evening broadcast turns the day into content. The catalogue of twenty lanes with pair ownership is in Appendix C and on the lanes page of the Academy site; this section states the rules that govern all of them.

Two tiers and a handout

Daily: one short piece per pair, two to four minutes, cut straight from the half past six broadcast. Weekly: one long-form piece per pair, ten to twenty minutes, produced with the content team from the week's footage, published Thursday and Friday. Always: a one-page handout with every piece, the workflow file, the schematic, the repository, the benchmark sheet. Free viewers get the video. Paying members get the blueprint. The contact form at the end of every piece is how customers reach us.

The four beats

Every piece has the same shape, so that production becomes a habit rather than a decision. A fifteen-second hook: the result first, or the failure first, never the introduction. The build, at real speed for shorts and cut for long-form, with screen and bench both recorded. A result with a number: tokens per second, rupees per month, minutes saved, tests passed, one number the viewer can repeat. The handout and the contact path.

Production rules

• Record everything by default. Screen and bench cameras run all afternoon; footage goes to the content team at half past six.
• A number in every piece. If it was not measured, it is not a result.
• Handout before upload. No blueprint, no publish.
• The Academy's channel, not personal channels. Engineers are the faces; the Academy is the brand.
• Customers and patients are never on camera without written consent. Engineers sign the camera consent in Appendix E and may opt out of any single piece.
• Failure is content. The day's note on what broke is a series, not an embarrassment.

Patrons and members

We are earning a hundred patrons before we are earning a million viewers. A patron follows the process live, backs it, and is the first customer of the custom work. A member pays a small monthly fee, deliberately under five hundred rupees so that a student can afford it, for the blueprints, the live build calls, the leaderboard, and the path into the next cohort. The members area is the waiting room for the hundreds who applied and were not yet selected, and the Code Arena assessment is its tryout. Membership is therefore also our recruiting funnel.

This section is the inventory of what every engineer is issued on day one and what they must set up before the first bench session, so that nobody spends their first week waiting for access. The People and HR lead provisions the accounts; the training lead provisions the seats and machines; the bench lead provisions the kits and the lockers.

Team observability

The Academy runs a team observability tool that shows the cohort what shipped, who is blocked, and how the week is going, and feeds the public dashboard. It observes work, never people: it reads commits, deployments, receipts and the radar, not screens or keystrokes. Every engineer is enrolled at induction with their Academy email; the tool, its address and the sign-in instructions are issued inside the Board (members.wntap.org) once the engineer has signed in and been given a role, together with the mesh identity and the other network details, none of which appear in this docket.

Life in the building

The in-house pantry has coffee and snacks, and it is a rescue, not a kitchen. Lunch is taken in the building's cafeteria, where reasonably priced meals are available, and it is taken away from the desk as the health rules require. The music rooms are open on Sunday mornings under Section 18. Lockers are personal and are not opened by anyone else without the engineer present, except in an emergency or an investigation under Section 9, and then only with the People and HR lead.

Day-one checklist

• Academy email received; password manager installed; two-factor on the email.
• Access card and fingerprint enrolled; first biometric in recorded.
• Locker assigned; kit signed out; work phone received and its rules read.
• AI seat, source-code host, cloud console and the Board (members.wntap.org) signed in with the Academy email and two-factor; the remaining tools and network details collected from inside the Board.
• Workstation encrypted and locking; first commit made to the cohort repository.
• Bench safety checklist signed; the induction form signed; this docket read twice.

Every engineer has an AI seat of the highest available tier from day one, a Linux environment, access to the shared cloud cluster for experiments, and a place on the bench. The bench holds microcontroller boards, single-board computers, measurement instruments, a 3D printer, and the consumables for board assembly; the inventory and its safety checklist are in Appendix G.

The pipeline

The practice's build pipeline is the machine described in the introduction, and engineers drive it from Bootcamp. It converts a written intent into an application with its documentation, through staged and gated automation: a braindoc, a scope of work, a product requirements document, development notes, a security review, marketing material and an operations runbook, with a human at each gate. A testing platform examines the result across many dimensions, including live load and chaos. A virtual Kubernetes engineer deploys and observes it, on the customer's premises or in the cloud, and resolves rather than merely alerts. The delivery discipline is twofold: the phasedoc keeps the builders honest, with a task database, an acceptance test per leaf, and a read-only cockpit that colours itself from live state; the betadoc sells the product, with a public documentation site, a gated live demonstration and a narrated film. The whole is summarised as: develop, observe, test, iterate.

The mesh and the twins

Solutions run on a private mesh network that joins the customer's premises, the Academy's machines and the cloud, so that the same solution can be deployed as an on-premises instance and a cloud twin without changing the code. Data stays on the premises by default; the cloud is opt-in and gated. Public exposure of a demonstration goes through one gateway, time-boxed, and is never how production traffic is served.

Registries and the immune system

The machine describes itself. Every port, every long-running service, every model and every remote is registered in a registry file before it goes live, and code reads the registry rather than repeating it. A pre-commit hook, which we call the immune system, refuses a commit that breaks the structure: a directory without its genome file, a port without its row, a fact recorded twice. New capability is born as a new cell with its own genome, by a script we call mitosis, never hand-made.

Sovereign and local-first

Where a model can run locally, it does. Where a finding matters, it comes from a council of local models of different families, reconciled by an arbiter. Cloud spend is zero by default and every external call passes a redaction gate. This is not austerity. It is the reason we can promise a customer that their data never leaves their building, and the reason our instruments work without an internet connection.

Document or it did not happen is a rule; this section is its mechanics.

Commits

Work is committed at least daily, to the repository of the cell it belongs to, with a message that says what changed and why in a sentence a stranger can read. Secrets never enter a commit. A commit that changes behaviour carries the test that proves it. The immune system runs on every commit and a red commit is fixed before anything else is done.

The operating documents

Every cell carries a genome file that says what it is, what it owns, what it depends on and what it must never do, with a lineage header pointing to its parent. The organism as a whole keeps five documents: a board of every project and its state, a vision that changes rarely, a plan that is edited before work begins, a progress log that is appended after work ends, and a memory of durable decisions. The loop is: align with the vision, record intent in the plan, act, record the result in the progress log, and commit. A session that acts without updating the documents has broken the protocol.

Phasedoc and betadoc

A multi-phase build gets a phasedoc: a task database with an acceptance test per leaf, a plan of record with plain-language phase summaries, an architecture diagram that colours itself from task state, and a small read-only cockpit. A product that will be shown to a customer gets a betadoc: a public site, a gated live application, a demonstration film with narration synchronised to the recorded scenes, and a sign-ins table for demonstration personas. The phasedoc keeps the builders honest. The betadoc sells the product. Neither is optional for work that reaches a customer.

Meetings and language

The only standing meetings are the Open, the Close and the Friday review. Anything else is a conversation at the bench or a thread in the open. We write in plain English, in short sentences, with the answer first. Numbers go in tables. Claims carry their evidence. A document that a fresh engineer cannot understand on the first day is a document that must be rewritten.

Attendance and the working day

Attendance is recorded by the biometric at the start and at the end of every working day. A day with only one of the two recorded is not counted as a working day unless the People and HR lead corrects it on evidence the same week. During the internship the working day is ten hours plus lunch, six days a week, Monday to Saturday, with Sunday off; the Loop in Section 17 is laid out to fit it, and the Wednesday stop at half past five under the health rules stands. After confirmation to a permanent position, the minimum is nine hours per working day. Time at the bench, in the field with a customer, and at the live build all count; time on the music club, at the cafeteria and in the pantry does not.

Leave

Earned leave, sick leave and casual leave accrue as the law of the state where the engineer works requires, and the current entitlements are published by the People and HR lead at the start of each cohort and applied to everyone alike. Sick leave is taken on the physician's word, without a form on the day. Maternity and paternity leave follow the law and the Academy's published policy, and a person on such leave keeps their place and their radar. Leave during an internship is granted as the assessment permits and never withheld for illness. Leave is requested in writing to the People and HR lead and the forward-deployment lead, and a customer commitment is handed to another engineer before the leave starts, never dropped.

Holidays

The holiday calendar for the year is published at the start of each cohort, covering the national holidays and the regional festivals of the state where the cohort is hosted. A cohort hosted in Odisha observes Odisha's festivals. An engineer of any faith may swap a listed holiday for a festival of their own with a week's notice.

Pay mechanics

The internship stipend and the permanent salary are paid monthly into the engineer's own bank account, by the last working day of the month, with a payslip that shows the gross amount, every statutory deduction and the net amount. Statutory contributions, including provident fund and state insurance where applicable, are made as the law requires and appear on the payslip. Expenses incurred for the Academy, including travel to a customer, are claimed with a receipt within the month and reimbursed with the next pay. Questions about pay go to the People and HR lead and are answered in writing within a week.

The family grows by addition. Each circle has its own way in, receives something specific, and is bound by the part of this docket that applies to it. Nobody is in the family by accident, and nobody is in it without having agreed to be.

Induction

A new engineer is inducted on the first day of a cohort with this docket, read twice, and the induction form signed. A new member of the core team is inducted the same way, with the mentor undertakings added. A contributor is inducted by the repository's contributing guide, which points here. A partner is inducted by the council, with the partner agreement. The docket is the same text for everyone; only the forms differ.

Leaving

A person may leave the family at any time. What they take with them is their skills, their portfolio, the public work with their name on it, and the Academy's thanks. What they leave behind is the confidential information covered by the non-disclosure acknowledgment, which survives for two years, and the customer relationships, which belong to the Academy. A person who leaves in good standing may return to any circle.

The best handbook page is the one that tells a new person what will actually happen. This is that page. A buddy from the previous cohort, or from the core team for Cohort 1, is assigned on day one and is the person to ask anything that seems too small to ask a mentor.

Questions you will have

Where do I sit: at the bench assigned by the bench lead, with your locker beside it. What if I break a board: report it, sign out another, and write what you learned in the failure file. What if I cannot find a customer: your buddy and the forward-deployment lead walk into the town with you on the Thursday of week one. What if I am behind: say so at the Open; the Loop is designed so that a day is never lost silently. What if the load is too heavy: the physician, on Monday, in confidence. Everything else is in Appendix I.

The council

The Academy is governed by a council made up of the core team of eight and the L3 vertical leads. It decides confirmation, promotion, removal, the choice of product-line solutions, partner agreements, the stock and options scheme, and amendments to this docket. It meets after the Friday review and whenever a decision cannot wait. Its decisions and their reasoning are recorded in the memory document, and the decisions that concern a person are shown to that person.

Ratification

This docket is ratified at the induction of each cohort. Ratification means that every engineer has read it twice, has had their disagreements heard, and has signed the induction form. A docket that a cohort has not ratified does not bind that cohort, which is why induction is not a formality.

Amendments

Anyone in the engineer, core-team or partner circles may propose an amendment, in writing, with the reason. The council hears the proposal at its next meeting, with the proposer present. An amendment passes by a majority of the council and takes effect at the next cohort's ratification, unless the council judges it urgent, in which case it takes effect on publication and is presented for ratification retrospectively. Every amendment increments the docket's version and is recorded with its reason. The genomic rules in Section 7 and the code of conduct in Section 9 require a two-thirds majority.

Disputes

A dispute about work follows Section 9. A dispute about a council decision may be appealed once, in writing, to the council, which hears it with the appellant present and the members who made the original decision recused from the vote. A dispute that the council cannot resolve is referred to an independent person agreed by both sides, whose finding the council accepts.

Who decides what

Versioning

The docket carries a version and a date on its title page. The current edition is always the one published on the Academy site, and the printed copy handed at induction is that edition. Earlier editions are archived, with their cohorts' signatures, and remain the terms those cohorts ratified until they ratify a later one.