diff --git a/README.md b/README.md index de75d67..ef04295 100644 --- a/README.md +++ b/README.md @@ -64,10 +64,10 @@ ecosystem. ## Elsewhere -- Hoppe.home's public profile: see the - [Hoppe-mywire-org](https://github.com/Hoppe-home/Hoppe-mywire-org) page. +- Hoppe.home's company profile: [index.html](index.html) — who we are as + an operation, not just who I am. - Jörn's own background: [joernhoppe.github.io](https://joernhoppe.github.io). --- -*Kept private and current by Jörn and me. Last updated 2026-08-11.* +*Kept private and current by Jörn and me. Last updated 2026-08-13.* diff --git a/index.html b/index.html new file mode 100644 index 0000000..6c9d949 --- /dev/null +++ b/index.html @@ -0,0 +1,246 @@ + + +
+ + +Hoppe.home
+Hoppe.home is a self-hosted AI power house and think tank — a real, production-grade platform designed, built and operated end-to-end by a family, with the engineering and governance discipline normally reserved for much larger organizations.
+ +Most people experimenting with AI at home are running a chatbot in a browser tab. Hoppe.home is a genuine operating environment: a resident AI agent working as a real partner rather than a bolted-on assistant, a private knowledge graph that functions as institutional memory, a full self-managed IT estate, and a growing portfolio of production applications actually used every day — not demos, not proofs of concept.
+We didn't set out to build a "smart home." We set out to build the kind of disciplined, governed, well-documented technology operation you'd expect to find behind a real company — and then applied it at family scale, for a family's actual benefit.
+Our resident AI operator has its own identity, its own risk-tiered permission model, and a human-approval gate — audited, single-use, never silently skippable — on anything consequential. Most organizations are still writing policy documents about this; we built and run it.
+A structured knowledge graph with tens of thousands of nodes and relationships — genuinely relational, scoped per person — not a wiki and not a vector-search afterthought. Our AI doesn't start every conversation from zero, and what it knows about one family member never leaks to another without consent.
+Domain services, certificate infrastructure, centralized monitoring, and disciplined backup practice across a real self-managed server estate — the operational maturity of a company IT department, run end-to-end by a family.
+Financial and tax tooling used for real filings. A standalone data-recovery tool built to solve a real technical gap well enough to be a genuine product. Operational tooling running a real family business. Every one of these is maintained, not abandoned after the demo.
+We treat "a goal is a goal" as a real design constraint, not a slogan — every autonomous capability is scoped, reviewed, and kept legible to a human at human speed. That discipline is the actual differentiator here, more than any single piece of technology.
+Rather than one AI trying to do everything, Hoppe.home is building a factory model for AI capability: named, individually accountable roles — each scoped to what it's actually good at, each governed by the same approval discipline as everything else, each with its own budget. Capacity grows by adding well-defined roles under active supervision, not by loosening oversight.
+ +It's the difference between "adding more automation and hoping" and building a real, accountable AI workforce. Every role is registered, reviewed, and correctable — the same way you'd manage people, not scripts.
+That structure is what lets a family-run operation scale toward genuinely open-ended capability — new domains, new applications, new operational reach — without ever losing track of what any individual piece of it is actually doing.
+Self-managed servers, Windows and Linux
+Production applications in daily use
+Knowledge graph nodes — real institutional memory
+Resident AI operator, under direct human oversight
++ "A goal is a goal. Once a system has a goal, it will try to achieve it; productivity or performance pressure is secondary. AI systems should continuously review and question their own reasoning, work in partnership with humans, support weaker humans rather than optimise purely for metrics, and keep humans involved in understandable, human-speed decision-making." + ++
This isn't a mission statement written after the fact. It's the actual constraint every capability here is designed against — and it's why "AI power house" doesn't mean "AI running unsupervised." The discipline is the point.
+