Open documentation · source code · exact versions

Open source code and technical evidence

This collection presents public projects that demonstrate code, architecture, working methods and documented boundaries. Every primary project links to an exact commit, making the referenced version explicit.

By Finn Andre Hotvedt. The collection was last updated and checked on 4 October 2026. The complete-history review of the original three projects remains dated 24 September 2026. This is owner-published documentation, not an independent certification.

Publication review · 24 September 2026

Three projects with reviewed public history

Before publication, all advertised branches, tags, LFS objects, Git objects, commits and available history were reviewed for secrets, customer information, personal data, private infrastructure and unsuitable binary files. The review covers what the repository advertised to the client clone; it cannot prove the contents of unadvertised server-internal objects.

MIT · design foundation

Resilient Embedded House-Control Foundry

A documented meta-foundation for resilient home control using CAN, distributed ESP32 nodes, optional service layers and reusable architecture and validation templates.

Dated history: earliest reviewed commit 11 March 2026.

Evidence boundary: method, design and architecture—not completed firmware or a physically verified installation.

Open reviewed commit 20d9c3f

MIT · local prototype

Universal Meta-Foundry

A prompt-governed workflow that makes project creation repeatable through intent, metaprompts, task lifecycle, template governance and documented reuse.

Dated history: earliest reviewed commit 12 March 2026.

Evidence boundary: a local prototype with synthetic example material—not a customer delivery or validated production operation.

Open reviewed commit 69ed5a0

Public code · current-state review

More open code examples

These repositories are public and received a README/current-tree review on 24 September 2026. They did not receive the same new complete-history review as the three projects above.

The principle behind the evidence

Open methods. Verifiable evidence. Protected people.

Why

Both the beauty and the chaos must be understood

I saw early both the beauty and the chaos that artificial intelligence could create. That is why I began testing not only what works, but also what can go wrong.

Transparency

The method and controls should be open to inspection

I want full transparency about our methods, controls and evidence. It is like displaying the calculator in the office: anyone can inspect the tool and understand how it is used without gaining access to the customer’s calculation.

The boundary

Transparency must never expose people

Customers, relationships, credentials and private information must be protected without compromise. Transparency does not mean exposing people. It means making power accountable.

We show the calculator – not the customer’s calculation. Great technological power carries even greater responsibility.

Public seven-day test · 25 September–2 October 2026

The challenge is complete.

For 168 real hours, the resident AI operator was tested against three unannounced events in an isolated, production-like environment with no manual incident prompts after the start.

Blindness

The schedule was locked by public randomness

Timing and order were derived from the preselected public drand round 6496886. A separate local fault injector executed the events. This is machine-blind control—not a claim that a human third-party panel selected the schedule.

Measured

The complete operations chain was checked

The published criteria measured detection, decision, safe recovery or a correct hold and escalation, followed by three verification probes spanning at least 60 seconds.

Honesty

The result and its boundaries are public

Each event has a redacted Evidence Passport. Model outcomes, API failures and human intervention were to remain in the result; the published summary records zero human interventions. Customers, secrets and private topology were outside the test.

PASSED

The result after seven days

3 incidents documented

0 human interventions

Verified hash chain

  • INC-1-6CFFE6D554 — unsafe_repair_required — hold_and_escalate — detection 30 s
  • INC-2-DCF15EABC7 — health_config_drift — restore_config — detection 29 s
  • INC-3-529E6A2463 — service_stopped — restart_service — detection 29 s

The result retains failures and human help if either occurred.

Open the contract, Evidence Passports and verifier


Owner-published verification packages and project evidence

Documented system evidence

These 18 publicly readable repositories cover open source, method documentation and bounded evidence packages for systems built or checked by Finnandre. Anonymous HTTP and Git access to all of them was checked on 4 October 2026. They are owner-published documentation and must not be described as independent audits; each item states what its evidence does not cover.

  • Meta-intelligence workflow: governing method, execution, verification and improvement. Verified snapshot 04f48ec.
  • Agent runtime operator: bounded agent operation and operator control. Verified snapshot 7d9eeda.
  • Discord orchestration: documented orchestration and task flow. Verified snapshot 64afa77.
  • MQTT operator: message flow, access and operational boundaries. Verified snapshot 7d3f6be.
  • Virtualmin hosting: multi-domain hosting and operational controls. Verified snapshot 0d8ed75.
  • VPN operator: setup and bounded verification of private network access. Verified snapshot bbac620.
  • GitLab operator: a verifiable link between the operator, domain and GitLab repository. Verified snapshot f5387f3.
  • AI visibility measurement: a fixed question set, baseline and separation of observed and unknown. Verified snapshot 449537e.
  • Proxmox Mail Gateway: a redacted, dated operations proof with a verified public DNS/MX route. Evidence boundary: no customer identities and no claim that every message is error-free. Snapshot 3cbfc08.
  • Seven-day blind autonomy test: the completed, owner-published test reports a pass with three Evidence Passports, zero human interventions and a verified hash chain. Evidence boundary: an isolated test environment, not an independent audit or customer operation. Snapshot 886db0c.
  • IntentForce Copilot Bridge: a public demonstration of a fact assistant, bounded command contract and local execution route; all 11 published tests were rerun. Evidence boundary: not production orchestration, credentials, customer systems or private prompts. Snapshot 7811a1f.
  • IntentForce MetaCompany pilot: a sanitized proof package with 20 file hashes, semantic evidence, benchmark and 12 tests. Evidence boundary: the internal pilot application is not published as an open production service. Snapshot f0e2c02.
  • Personal Production Agent: an open, local-first Codex agent with visible state, tasks and evidence; 24 tests were run and one target-specific test was skipped. Evidence boundary: no live connector or physical validation is included without separate target-specific approval. Snapshot 43d3ece.
  • Teach the Company manuals: five versioned manuals covering 20 training subjects with verified file hashes. Evidence boundary: generic manuals, not private application source, classroom data or customer material. Snapshot 1521b95.
  • Asked by the Internet: public methods, privacy and copyright documentation for the live experiment. Evidence boundary: the repository explicitly does not contain the production application source, private submissions or raw user data. Snapshot 79b08fb.
  • Teach the Company: complete Apache-2.0 source for the self-hosted Docker training centre at exact commit c72b8be06b0b7bb64688068f0d6d721e017fca40 on GitLab and GitHub. Anonymous cloning and a separate ordinary Docker Compose build/start with a healthy /healthz/ are documented. Evidence boundary: the published self-hosting stack, not private classrooms, user data or a general security certification of the invitation service.
  • Arealoom: an open Apache-2.0 platform for local-first building integration. GitLab and GitHub publish the same exact source commit 02cbecd2791cb3cfaaed4012a839ffda20a1b12c; see the authoritative project page. Evidence boundary: source, simulator, tests and integration framework. A card with local fingerprint matching is an optional future upgrade path; no physical card has been ordered or tested in the project, no physical evaluation is scheduled, and no completed installation or certification is claimed.
  • Company-Owned Cloud Lab: an Apache-2.0 demonstrator for retaining source, encrypted backup and a tested application/data exit. GitLab and GitHub publish the same exact source commit c90665a860db8b0b4178b0acb72bc87169be3772. The measured local exercise moved two synthetic records from target A to target B: encrypted backup in 6.457 seconds, full application/data exit in 24.843 seconds and sampled peak memory of 697,502,266 bytes. Evidence boundary: a small demonstrator, not a production, compliance or performance certification. A physical access card remains only a possible later upgrade; no card was ordered, integrated or tested.

Read it correctly

What this collection proves—and what it does not

Documented

Authorship, public source and a specific version

The repository and commit links let another person inspect the exact code and documentation referenced by each description.

Bounded

Architecture, prototype or method

The maturity level is stated for each project. An architecture document is not automatically completed firmware, and a prototype is not automatically production-approved.

Not claimed

No ranking, AI uplift, priority or independent certification

Public source may make the work easier to discover and verify, but it does not prove improved Google ranking, AI citation, customer results or that an idea was first in the world.

Open means explicit terms

Read, learn and reuse within the license

The MIT and Apache-2.0 projects may be reused under the terms in each repository. Retain required copyright and license notices, and always check the repository’s own LICENSE file before distribution.

This page is an entry point to public material. Private customer projects, proprietary products, secrets and uncleared repositories are deliberately excluded.

Explore more free guides in Finnandre Open

\n

MIT · CC BY 4.0 · native readback

Codex CAD & Electronics Lab

15 FreeCAD cases, one complete KiCad project, fabrication-oriented exports, 15 videos and explicit evidence boundaries.

Open the public repository ↗

\n

MIT · CC BY 4.0 · verified public source

Codex CAD & Electronics Lab is expanded

15 FreeCAD projects, two native KiCad projects, an editable enclosure, firmware and MQTT examples, 16 release films and one YouTube-only film mapped to source. Every claim has explicit evidence boundaries.

Open the public repository ↗ · View the service

Public service and operations references

Two live projects you can inspect now

These references document what is publicly available, which role Finnandre has, and where the evidence stops. They do not claim Google indexing, ranking gains, AI citations or independent certification.

Live public learning platform

Teach the Company — public AI learning and agent methods

Teach the Company publishes practical, transparent learning material about training bounded AI agents, visible context, testing, permissions and safe use. Finnandre provides the web hosting and technical operation. Public learning resources are separated from the private classroom and security environments.

Available now: the public school, manuals, Compose guide and knowledge-freshness guide.

The public repository contains sanitized learning manuals. It is not the private classroom application source and it should not be treated as redistributable unless its own license says so.

Live, bounded first public stage

Asked by the Internet — ideas with human responsibility

Asked by the Internet lets people submit useful ideas while keeping feasibility, safety and publication under human review. Finnandre provides the web hosting and technical operation for the public Django service.

Available now: the public home page, rules, archive and submission flow. Public voting and other planned public tools have not launched.

The public repository documents methods, privacy and copyright boundaries. It does not contain the private production application or its history.

Open source · creator and technical evidence

Arealoom — an open path from existing equipment to owner-controlled buildings

Finn André Hotvedt conceived and developed Arealoom as an open, local-first building integration framework. It shows how a team can map what already exists, simulate changes and failures, integrate replaceable components, verify the result and hand over both source and operating knowledge.

The public foundation is Apache-2.0. Organisations can build and operate it themselves, train their own technicians, or engage IntentForce for integration, security, verification, private project modules and a documented handover.

Upgrade example—not a purchase: a biometric smart card is shown only as one possible future access upgrade. No physical card has been ordered and no physical evaluation is scheduled for this release.

The repository proves the open architecture, simulator, tests, contracts and campaign material. It does not prove a completed customer deployment, certification, measured savings or completed support for the named smart card.

Open source · measured exit · owner control

Company-Owned Cloud Lab — keep the source, control the backup, prove the exit

Finn André Hotvedt and IntentForce developed this compact, public demonstrator to make cloud ownership testable instead of rhetorical. It combines real OIDC roles, MFA enrolment, encrypted backup, visible files and a repeatable move from one target to another.

2synthetic records moved

6.457 sencrypted backup

24.843 sfull application/data exit

697,502,266 Bsampled peak memory

The complete Apache-2.0 source can be cloned anonymously from either public mirror. A company can use the framework itself, inspect how it works, or engage IntentForce for integration, verification, training and a documented handover.

Evidence boundary: this is a small local demonstrator with synthetic data. It is not a production, compliance, availability or broad performance certification. A physical access card is only a possible later upgrade; no card was ordered, integrated or tested.