We create and publish AI skills and companions to hand to your own AI or follow by hand. We build interactive tools, software, the shared services the ventures run on, and the data and methods behind them.
Complete, open methods: download the skill and put it to work.
When a practice wants to cut what a Medicare between-visit program costs to run without cutting care, decide what to automate first, find out whether it really needs another coordinator or nurse, or stop a monitoring or alert stream from…
When the user wants to decide which tasks or capabilities their team should automate with AI, which need human review or decision rights, and which AI is quietly eroding versus strengthening as a real advantage.
When the user wants to execute or rehearse a Bare Metal Software Day 2 operational procedure against their own system - restoring from backup, rotating a secret, shipping a hotfix, onboarding or offboarding a customer, handling a vulnerable…
When the user wants to audit or design their application's security posture using Bare Metal Software's "four attackers" model and crown-jewels framework, including mapping defaults to a regulated buyer's security questionnaire.
When the user wants to set up an AI Chief of Staff for a software project - a persistent reasoning layer that watches a repository's specifications, decisions, issues, tests, and meetings, and reconciles them, without becoming the project's…
When a technology leader wants to build a real, living engineering playbook — starting with version control, code review, and CI/CD — instead of a rulebook nobody reads, or wants to audit an existing set of engineering processes and set up…
When the user wants to plan the acceptance-to-day-90 onboarding of an incoming CTO (or comparable technology executive) - building the entry brief, a bounded first-month learning plan, a day-30 mandate check, and a day-90 assessment…
When a practice runs, ran, or is arguing about a Medicare between-visit program (chronic care management, transitional care, remote monitoring, APCM, behavioral health integration, and the like) that underperforms, "doesn't pay," or looks…
When the user has complaints, feature requests, Support tickets, CRM notes, or customer success notes about a workflow and wants to know what is actually wrong before anyone builds a fix.
When a practice is about to launch, restart, or add a Medicare between-visit program, has inherited one it didn't design, or has a pilot that has run without a decision, and wants a plan that starts with one program and one cohort and grows…
When a technology leader is stuck in a "should we decide this now or keep our options open" argument, or when a real tradeoff — build vs.
When the user wants to define what a CTO role actually is before hiring, evaluating, or restructuring one - building a decision-rights map and a written CTO mandate instead of a generic job description, and a stated recommendation on whether…
When a medical device manufacturer's product, systems, quality, regulatory, postmarket surveillance, or complaint team wants to know what evidence a device produces, what its quality and regulatory work needs that the device doesn't produce,…
A skill for the engineers and operators of a Discoverability Engineering system, which audits the repository and live public surfaces and returns a status for each required capability, with proof, what is missing, and the smallest fixes in order.
A skill for the Discoverability Operator that builds the question benchmark a Discoverability Score runs on, drafting finder questions from real inputs, reviewing them, and ending with a recommendation to freeze the benchmark or not.
When the user has a scored Discoverability Score run and wants to know why the subject is or is not surfaced, what to change, and how to retest.
A skill for the person scoring a Discoverability Score baseline or retest, which takes a frozen benchmark and the raw answers captured from engines, records the evidence, runs the scoring script, and ends with the score and its confidence notes.
When an editor wants to sort their own work into scarce human judgment, AI-assisted judgment, abundant machine labor, and obsolete process overhead, and find what to hand off first.
When an editor is considering a consequential edit to a manuscript and wants it tested against evidence before it delays release: a structural change, a claim change, a positioning change, or a change of voice.
When the user wants to know whether a claim-shaped search would find one of their public disclosures, the way a patent examiner or a challenger would search.
When the user wants to test whether something their organization calls "strategic," "proprietary," or "a real advantage" actually is one — a system, dataset, process, team, or roadmap claim they suspect might just be a story the company…
When the user wants a first-pass patent screen of a supplier, partner, or planned piece of work before qualifying it: which patents and published applications does the other party hold under every name variant, and which of their claims use…
When a practice running a Medicare between-visit program (chronic care management, remote monitoring, transitional care, APCM, behavioral health integration, and the like) wants to check each month that it is billing for real, needed,…
When a defense leader, program office, unit, or defense-tech company wants to decide who should integrate one class of system (industry, industry with warfighters judging, a Warwright team with reach-back, or a Warwright team at the unit).
When an editor or imprint owner needs a one-page Metadata Brief for a book before release: the reader, the promise, category choices with reasons, keywords, the description, price band, comparable books, and format and ISBN decisions.
When the user wants to figure out what their organization's real competitive advantage is, run a "Native Alpha audit," find out whether a claimed strength is actually evidence-backed, or produce a current, defensible statement of what the…
When a hospital or health system buyer (healthcare technology management, clinical engineering, procurement, IT security, or a clinical or process owner) is evaluating an institutional medical device and wants to know whether to buy it.
When a practice needs to decide whether a Medicare between-visit program (chronic care management, remote monitoring, APCM, transitional care, and the like) will pay for itself before it hires, buys, restarts, or switches, or wants to…
When the user wants a public disclosure (a technical note, page, paper, or document the company has published) written up as a Prior Art Record, so an examiner or a challenger can find it and prove when it went public.
When the user wants to decide whether to keep, replace, or drop a specific dependency (an SDK, ORM, wrapper library, or framework) using Bare Metal Software's protocol-first and build/depend/generate decision method.
When the user is about to make an invention, method, or technical result public and needs the choice laid out first: file a patent application, publish defensively, or keep it a trade secret.
When an editor or imprint owner has a manuscript that might be ready to ship and needs its open issues sorted into blocker, fix if practical, next edition, or ignore, and needs a release recommendation with reasons.
When the user wants to run a structured, evidence-based CTO (or comparable technology-executive) search - building a weighted scorecard, interview guides, a work-sample case, a reference plan, an evidence summary per candidate, and a stated…
When the user wants to run a 90-day, 180-day, or one-year review of a sitting CTO (or comparable technology executive) against their original mandate - organizing evidence by the book's own review questions and role-specific criteria…
When a medical device manufacturer's systems architects, safety engineers, software engineers, or security engineers want to check a connected institutional device design before the design freezes, or before a change adds a network dependency.
When the user wants to choose or write down the feature defaults for a new AI-native application in the Bare Metal Software style - sign-in, roles, tenancy, audit trail, files, search, reports, backups, jobs, and the rest of the two-dozen…
When a technology leader wants to figure out what to coach their team on next, run an honest perception audit of their own leadership (how the C-suite, their own team, and people outside their reporting chain actually experience them), or…
When the user wants to free up their team's time and attention by identifying recurring work — meetings, reports, approvals, custom systems, features — that no longer earns its cost, and getting a stated recommendation (stop now / pilot /…
When a field-built or team-built defense system has to survive its builders rotating out, before a team integrates a system or before any builder leaves.
When a technology leader is new to a seat (or hasn't re-checked in the last year) and wants to test whether the inherited story of "why this business exists" and "what competitive game we're playing" still matches reality — before making…
When a technology leader needs to decide, explicitly and per task category, how much autonomy to grant a specific engineer or a specific AI coding agent — instead of defaulting to "trust everyone" (hover) or "trust no one" (vanish), or…
When a technology leader wants to write (or rewrite) a real technology vision instead of a "mood board" roadmap slide — one built around the Native Alpha their company actually owns, with horizon lengths sized to how fast their specific…
A skill for product managers and their teams that grades every claim about users in a PRD, roadmap, ticket thread or other product document with a User Evidence Ladder level, and states which decision the evidence can carry now.
When someone holds a claim about what a unit needs (a statement of need, capability description, requirement, change request to a vendor, after-action comment, or test report behind one) and wants it graded before anyone buys anything.
When a team proposes a change to a business workflow (removing a step, adding a shortcut, a "streamlined" screen, a new required field, a free-text option, a redesign) and wants to know whether it is actually an improvement before it ships.
Work through a question in your browser; nothing you type leaves it.
A free browser tool from Intellectual Frontiers Press that turns a few answers about a business document into a review prompt that scores how much of it is specific, evidenced, and useful, and how much of it could have been written for any company.
Find and test a Native Alpha hypothesis, gather evidence across five connected operating units, and make a decision to continue, change, back, build, or stop.
A browser-only, evidence-gated Capital tool for deciding whether funding would accelerate a repeatable customer motion or merely extend the search for one.
Worksheets, tools and templates that go with each book, open to anyone.
Code you can download or use online.
A free browser tool that turns a few answers about a business document into a review prompt that scores how much of it is specific, evidenced, and useful, and how much of it could have been written for any company.
One engineering setup that installs the same way on Windows through WSL, Linux, macOS, in a container, or in a cloud agent session, with the shell, git credentials, repository layout, and everyday tools already configured.
The shared services our ventures and companies run on. You can use them too.
An open initiative for scientific research reproducibility. Companion executable source code repositories pair a published paper with the code, data, and documentation needed to reproduce it, turning static publications into living evidence.
The companion shared service we run when Revenue Engineering is too early. The outcome it owns is proven demand: a named audience, a claim that survives contact with them, and a first step they will actually take.
A governed evaluation platform for hospitals and health systems. Instead of a procurement queue full of unranked vendor claims, a health system gets structured evaluation: who has been vetted, on what evidence, against which internal need.
Finds reimbursed demand in healthcare and states it in the terms a business plan needs: the claims-defined cohort, the counties where the gap is largest, the CMS signal that proves it, the CPT and HCPCS codes and bundles that pay for it, and the revenue at stake. It is a shared service to every other venture and the intelligence spine of Fund II.
A healthcare growth and care-access capability that turns fragmented patient demand into timely, scheduled care. The team designs, launches, and operates AI-driven demand intelligence, orchestration, and routing on behalf of provider organizations, filling real provider capacity instead of reporting clicks and leads. The portfolio's ventures draw on it as the shared demand-and-access engine.
An execution layer that turns the Microsoft 365 or Google Workspace a provider already pays for into a working digital front door. The argument is that most organizations do not need to buy more healthcare software; they need the software they own to actually run the work. It serves the portfolio as the shared front-door capability.
The shared revenue capability every company in the portfolio draws on. We define an outcome, build an AI Workforce™ that owns it end to end, and run it on one platform with the same observability and reporting for every firm.
A continuous clinical research infrastructure platform that reads signals across consented health transaction data for earlier detection and continuous research. Payshent is its funding and consent layer; Symvion is the intelligence layer that turns compensated patient data into detectable signal.
The datasets, methods and landscape studies our staff, partners, services, software and solutions draw on.
Dataset
The claims-defined view of where reimbursed demand actually sits: cohort, county, CMS signal, the codes and bundles that pay, and the revenue at stake. It is the intelligence spine under Fund II, and an asset in its own right.
Study
Over a decade of innovation in precision learning and education has led to a significant surge in patent activity, with filings growing from 85 in 2014 to 1145 in 2023, marking a clear trend towards increased innovation and investment in this sector. Driven by a surge in demand for remote learning solutions during the COVID-19 pandemic, the precision learning sector has witnessed an unprecedented focus on developing and commercializing e-learning platforms recently, which is visible in patenting trends as well.
Study
Electronic Medical Records (EMR) systems are used for efficient and effective patient care management. However, with the increasing reliance on these digital systems comes a significant challenge: ensuring the security and integrity of sensitive medical data.
Method
Our method for turning a finding into an owned position: find, prove, decide, compound. It is a work in its own right, because everything else in this register was produced by running it.
Journals and periodicals we publish and operate.
The record of what systems actually do in the field versus what they are documented to do, which is where our findings start.
A health innovation discovery platform: crowd-curated technology, use cases, and market signal used as an intelligence surface, not a blog.
The standing argument that passing an audit is not the same as being secure, written for the people who own both obligations.
GovCon Intelligence Center (GovCon IC): the publication for how public agencies buy, modernize, and evaluate technology.
A healthcare media network of news, interviews, and vendor coverage written for the people who buy and run health technology, not the people who sell it.
The longest continuous record in the publishing program: a personal site where health IT arguments, field observations, and invention sketches have been published in public for two decades.