AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
The runtime, the flows and the benchmark for long-horizon agent work — and the results that say whether the flow works, in Lean, in CUDA and on Kaggle.
Developer toolsVue · TypeScriptGitHub @humanfiaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗The Humanfia website: the team, its projects and its results, built with VitePress. It is served at humanfia.ai.
Needs Node.js 22+ and pnpm.
pnpm install
pnpm dev # local preview
pnpm build # build into .vitepress/dist
Pages are Markdown: index.md, projects/, flows/, about/, and one file per
post in news/ or blog/. Files in public/ are published as they are. The Humanize page is
one component: .vitepress/theme/components/projects/humanize/.
The figures in the Flow Science post on the blog are drawn by
.vitepress/theme/components/flowscience/: a line chart with log and hand-spaced axes the post
kit does not have yet, and the data it plots, read off the charts in our talk slides
(deck-data.json, described in figures.ts).
The HMA page (projects/hma.md) is one full-width component,
.vitepress/theme/components/projects/hma/; its numbers live in data.ts there, each with its
source.
The KDA page (projects/kda.md) is drawn by its own components,
.vitepress/theme/components/projects/kda/; its numbers live in the page's frontmatter, each
block naming the write-up it comes from.
A post is one file, named YYYY-MM-DD-slug.md. Put results in news/: one result per post.
Put essays and arguments in blog/. Start the file with this frontmatter:
---
title: "What was done, in one line"
description: One or two sentences for the standfirst, the card, the feed and search engines.
date: 2026-10-05
authors:
- Your Name
tag: HOA
---
tag is the project the post belongs to. A news post credits more than its authors: its
byline, everywhere it is shown and in the feed, adds the leads and co-leads of every project
the tagged project is built on, transitively. An HOA result therefore also names the Humanize
lead, and a post about Humanize itself adds nobody. Projects, their tags, leads and
dependencies live in one registry, .vitepress/theme/projects.ts, which the team roster reads
too; a news tag it does not list fails the build. Everything else is generated from the frontmatter:
the post's page (its hero, contents, related posts and a Cite button that exports the
post in BibTeX, BibLaTeX, APA, MLA, Chicago, IEEE, RIS and CSL-JSON), the section index (a list for news,
a mosaic for the blog), the home page, and the section's feed (news/feed.rss, blog/feed.rss). There is no list to
update. A news post that adds an achievement: block also gets a tile in the home page's
Achievements, one per topic, from the newest post. Figures come from the post kit: interactive charts, tables, diagrams and callouts
that you write straight into the markdown. CONTRIBUTING.md is the guide to
the post layout and every component in the kit.
A push to main builds the site and deploys it to GitHub Pages
(.github/workflows/deploy.yml). Pull requests run the same build without deploying. The org
profile in humanfia/.github is generated from the deployed
site and notices a deploy on its own, so nothing here needs a token for it.
Issues and pull requests are welcome; see the contributing guide. Every pull request runs the build and three checks, and all four have to pass:
pnpm build # every internal link resolves
pnpm check:anchors # every #fragment resolves to a heading the site built
pnpm check:feed # the feed holds every post, and a click on it is not a 404
pnpm check:docs # every link out to the documentation reaches the page it names
The site's code — .vitepress/ (configuration, theme, components and checks), scripts/,
the workflows and the build configuration — is licensed under Apache-2.0.
The content — the pages in index.md, blog/, projects/, team/ and about/, and the
images under public/ — is licensed under
CC-BY-4.0: reuse it with attribution to Humanfia and a link to the page.
The citation styles in .vitepress/theme/csl/ are copied unchanged from
citation-style-language/styles and are
licensed under CC BY-SA 3.0, as each file
says.
Material quoted or linked from others (problem statements, benchmark results, third-party repositories and papers) keeps its owners' terms. The Humanfia name and logo identify the organisation; the licences above do not grant any trademark rights.