VIHAAN OS
The archive, in one frame
Four modules over a single live index. Nothing here is a copy — every row is the same published record the rest of the site is rendering, read through one query.
The archive keeps two clocks: when a thing happened, and when it was written down. Index reads by the second, Path by the first, and where they disagree the gap is shown rather than smoothed over.
58 entries
2 revised · 0 superseded
VIHAAN OSindex58 rows · last record 4d ago
Everything published, newest first by the date it was written down.
- Writingprint("Hello, World!")3 Aug 2026The first post. The start to growth.Written by hand
- Milestonevihaanvaghela.com2 Aug 2026The site you are reading. Weeks of work, most of it not the interesting kind.Written by hand
- MilestoneSwift, VECTOR Lite, and a physics exhibition1 Jul 2026I picked up Swift and started building native iOS — VECTOR Lite, with an eye on theWritten by hand
- MilestoneEXTREMIS becomes VECTOR15 Jun 2026Variable Environment Control Through Observation Response.Written by hand
- MilestoneThe Himalayas9 May 2026I went to the mountains and left the laptop behind.Written by hand
- Projectvihaanvaghela.com1 May 2026A personal archive built to outlast its own framework — CMS, essay pipeline, and an operator console with no URL.Written by hand
- Milestonev1 is real — 647,000 cycles, zero failures1 Apr 2026A two-hour adversarial stress test across more than 647,000 cycles. Zero failures.Written by hand
- MilestoneThe eight-protocol stack20 Mar 2026Sentinel, Serpentine, Aegis, Atlas, Mender, Phoenix, Hyperion, Terminus. OneWritten by hand
- MilestoneEXTREMIS V1, and writing it down as it happened4 Jan 2026The first real implementation, and — more consequentially — the moment I startedWritten by hand
- ProjectVECTOR20 Oct 2025An autonomous infrastructure system that monitors itself, contains its own failures, and narrows its own authority when it stops being certain.Written by hand
- MilestoneRajasthan20 Oct 2025We were driving back toward Ahmedabad after a trip through Rajasthan when we were in aWritten by hand
- MilestoneCopilot, Claude, and agentic coding1 Aug 2024Modern AI arrived, and programming came back — different from how it left.Written by hand
- MilestoneOverheard engineering15 Jan 2024My father worked remotely, and I did homework near enough to hear it.Written by hand
- ProjectmBot Neo, and the end of robotics1 Oct 2023A robot that worked, and the discovery that I did not care. The most useful dead end I have hit.Written by hand
- MilestoneBlockly, an mBot, and the end of robotics1 Oct 2023Blockly, and an mBot Neo. Line following, obstacle avoidance, a few behaviours of myWritten by hand
- MilestoneBack to India, into sixth grade1 Jun 2023I left fifth grade half-finished in the United States and returned to India in 2023,Written by hand
- MilestoneSelected for the IB pathway at Moody Middle School1 Nov 2022During fifth grade I was selected for the International Baccalaureate pathway at MoodyWritten by hand
- MilestoneThe Scratch years, and then the fade1 Jan 2021Two years of building things with no purpose beyond building them.Written by hand
- ProjectAttack of Excalius14 Sept 2020A Scratch platformer with hand-drawn sprites and a boss fight I never balanced. The first thing I finished.Written by hand
- MilestoneScratch14 Sept 2020On 14 September 2020 I opened Scratch for the first time. I was eight.Written by hand
- MilestoneElementary school, and no particular direction1 Aug 2017Four years in which nothing happened that belongs on a résumé, and which I would notWritten by hand
- MilestoneRichmond, Virginia1 Aug 2016We moved south, to Richmond, and I started at Short Pump Elementary School. I turnedWritten by hand
- MilestonePiscataway, New Jersey1 Jun 2015We moved to the United States when I was four. New Jersey first — an apartment complexWritten by hand
- MilestoneBharuch15 Oct 2011Born on 15 October 2011, in Bharuch, Gujarat.Written by hand
- VECTORWhy VECTOR existsStatic infrastructure fails in one way, adaptive infrastructure fails in another, and intelligence alone resolves neither. What is actually missing is governance.Drafted with assistance · reviewed
- VECTORThe philosophyThe six commitments encoded in the name — observation, response, variable environments, cognition, documentation, provenance — and why each one is there.Drafted with assistance · reviewed
- VECTORThe nameEXTREMIS to VECTOR. Why a name is a constraint on the thinking rather than a label on the result, and how to notice when yours has become the wrong one.Drafted with assistance · reviewed
- VECTORThe intelligence layerAnarchy, ORACLE, MORL, PULSAR, Fusion and Meta — five ways of being clever and one controller that decides how much cleverness is currently affordable.Drafted with assistance · reviewed
- VECTORObservation before actionThe first principle. A system may not act on a quantity it has not observed, and an observation is incomplete without its uncertainty.Drafted with assistance · reviewed
- VECTORExplainability before automationA component that cannot account for its output does not enter the decision path, regardless of how well it performs.Drafted with assistance · reviewed
- VECTORDocumentation is part of engineeringWriting the argument for a component before building it is the cheapest way to discover that it should not exist.Drafted with assistance · reviewed
- VECTORGovernance before intelligenceThe structure that constrains a capability must exist before the capability does. Retrofitting authority onto a working system does not work.Drafted with assistance · reviewed
- VECTORAdaptive systems over static systemsWhy the preference for adaptation is conditional rather than absolute, and what a system must have earned before it is allowed to adapt.Drafted with assistance · reviewed
- VECTORAtlasRebalancing. Redistributes load across healthy capacity, and knows the difference between a distribution problem and a capacity problem.Drafted with assistance · reviewed
- VECTORPhoenixRecovery. Brings the system back in dependency order, and deliberately restarts more than strictly necessary.Drafted with assistance · reviewed
- VECTORVisionWhere this is going over five, ten and twenty years — as engineering direction rather than ambition, and with the uncertainty left in.Drafted with assistance · reviewed
- VECTORThe human remains the operatorThe final principle, and the one the others exist to make possible. Authority is delegated, bounded, and returns to a person by default.Drafted with assistance · reviewed
- VECTORThe eight-protocol governance stackSentinel to Terminus: one escalation chain from the first anomaly to a permanent, human-authorised end. Every protocol has one role and nothing overlaps.Drafted with assistance · reviewed
- VECTORv1 — 647,000 cycles, zero failuresThe first working v1: a two-hour adversarial stress test with no failures, no crashes, no dropped events and no ordering violations.Drafted with assistance · reviewed
- VECTORThe latency crisis: one component, ninety-seven percentp95 of 100 ms to 1.124 ms. Six weeks of looking in the wrong place, and the component I trusted most turning out to be the entire problem.Drafted with assistance · reviewed
- VECTORA console with no URL, and why that is not securityThe operator gateway is reached by typing a trigger into the search bar. That is a user-interface decision, and saying so out loud is what stops it becoming the plan.Drafted with assistance · reviewed
- VECTORThe event busWhy the protocols communicate through a priority queue instead of calling each other, and what that buys when the system is under load.Drafted with assistance · reviewed
- VECTORThe hardware abstraction layerOne interface between the decision system and a physical signal controller — and why emergency override lives at this layer rather than above it.Drafted with assistance · reviewed
- VECTORAdversarial robustnessStatistical anomaly detection assumes sensors are noisy. This subsystem exists for the case where they are lying.Drafted with assistance · reviewed
- VECTORSentinelDetection. The first stage of the escalation chain, the only component that observes the system directly, and the one that nearly made the system unusable.Drafted with assistance · reviewed
- VECTORI stopped optimising, and built a way to stopPerformance describes a system under favourable conditions. Infrastructure only matters under the other ones.Drafted with assistance · reviewed
- VECTORThe data pipelineMulti-resolution resampling, feature engineering and walk-forward validation — and why the splitting strategy matters more than the model.Drafted with assistance · reviewed
- VECTORThe simulation layerWhy a system intended for physical infrastructure is developed against a simulator, and what a simulator can and cannot establish.Drafted with assistance · reviewed
- VECTORSerpentineClassification. Turns many independent signals into one judgement about system state, so that everything downstream reasons from a shared answer.Drafted with assistance · reviewed
- VECTORAegisContainment. The first protocol that acts — isolating and throttling to stop a local failure from becoming a systemic one.Drafted with assistance · reviewed
- VECTORWhat is VECTOR?The preface. What the system is as an idea, before any question of how it is implemented — and what it is deliberately not.Drafted with assistance · reviewed
- VECTORThe boundary between seeing and decidingMost failures in complex systems are not broken components. They are boundaries that were never properly drawn.Drafted with assistance · reviewed
- VECTORHow I reduced a complex system to seven variablesComplexity is easy to add and looks like intelligence. Most of it is redundant, and reduction is what survives degradation.Drafted with assistance · reviewed
- VECTORProvenance belongs in the schema, not the READMEWhy this site stores essays and VECTOR documents in two different tables, and why the publish path refuses rather than warns.Drafted with assistance · reviewed
- VECTORHyperionEmergency shutdown. Fires within one second, halts everything, and is deliberately the least sophisticated component in the system.Drafted with assistance · reviewed
- VECTORThe authority layer: discipline over chaosThe authority layer. When uncertainty rises, autonomy is deliberately narrowed — and the system has to earn it back in stages.Drafted with assistance · reviewed1 revision
- VECTORMenderRepair. The only protocol in the governance stack that uses a learned model — and the one most carefully constrained, by a budget rather than a rule.Drafted with assistance · reviewed1 revision
- VECTORTerminusPermanent termination, reachable only by a human. The system cannot invoke the end of its own escalation chain — and that is the most important property in the design.Drafted with assistance · reviewed