The Journal
Short records of what each research program observed, decided or found. A note is not a finding until an issue carries it.
Pattern
Setting up a companion code repository takes seven steps, and most research groups can do the first five in an afternoon once the analysis is finished. The steps go from storing the data in the right place to making the code rerun on new data, and the last one, automated checking, is optional.
Pattern
Code that can't be public, because of a patent plan, a contract or commercial value, can still be checked. Keep the companion repository private and invite the editor, the reviewers or the funder you choose. Software companies protect their code this way every day.
Theory
When evidence is thin or can't be checked, medicine leans on who said it: the senior author, the famous journal, the expert panel. When anyone can rerun the analysis and test it on new data, the question shifts from who said it to what the evidence keeps showing.
Theory
Most peer reviewers can't spend days rebuilding an analysis. Automation can take that load, but only if it's built in the right order: rules that a program checks without judgment first, a model only for what rules can't answer, and a person last. A higher layer never overrules a lower one.
Pattern
Split a study's materials by risk: data about individual patients goes to a repository built to control access to it, and everything else, the code, the metadata and any data with no patients in it, goes in the companion repository beside the paper. The split puts the governance burden only where the risk is.
Pattern
Many published analyses were done in a spreadsheet, not in code. That's fine: a spreadsheet with its formulas intact, its data in open formats and a short README that says the order of the steps is a companion repository too.
Theory
A published paper is a snapshot. A companion repository can keep going: each time the same method runs on new real-world data, the authors publish a new release with its own DOI, and the release the paper cites never changes. Peer review keeps its job, and readers can see whether a finding still holds.
Pattern
Machines can watch systems and prepare evidence. People remain responsible for decisions that cannot be reversed. This note recommends that machines take the high-volume, repetitive work where errors can be corrected, and that the line between machine and person move only when measured performance supports it.
Theory
Retention and deletion policies often exclude backups for practical reasons. The exclusion is defensible. Leaving it unstated in the notice is not. Backups usually hold the data a policy says is deleted, so a privacy notice that is silent about them misleads the people it describes.
Theory
If withholding consent does not change what a system does with a record, the consent mechanism only keeps a record of the choice. It does not enforce it.
Theory
Serious intrusions usually end with rotating every credential, key, token, certificate, and service account. Most organisations have never attempted this even partially. Full rotation is disruptive, which is why it is skipped, but a bounded drill on one class of secret shows what breaks before an intrusion forces the issue.
Pattern
A verified end-to-end deletion exercises the data map, the vendor list, the backup policy, and the derived-data problem at once. Few organisations pass it on the first attempt.
Theory
A recovery objective is a statement of intent written during planning. The useful number is the one produced by the last real restore, with the date attached.
Pattern
For each control that depends on a person recalling guidance under pressure, look for a technical arrangement that makes the safe action the default or the only one.
Theory
People often ask for one weighted score. Publishing it before the measures are validated would give an untested formula the look of certainty. This note recommends publishing the measures and the unanswered questions until results show which measures tell us something on their own.
Pattern
Contacts leave, numbers change, portals replace phone trees, and contracts renew with different terms. An untested escalation path is an assumption with a date on it.
Pattern
A screenshot is a claim about a moment. A stored query with provenance can be re-run by the reader, which changes what the evidence is worth.
Pattern
Counting open findings measures the discovery process. It says nothing about detection speed, containment, or recovery, and it falls when scanning stops. An executive dashboard should therefore show detection time, containment time, and demonstrated recovery, because a falling finding count does not show a safer company.
Theory
A generated security assessment reads better than a human one and is harder to doubt. Readability and correctness are unrelated properties. The risk is that AI output raises confidence faster than it raises capability, so every generated claim should carry its source record.
Theory
When requirements are mapped to operational data sources, the largest category is usually requirements that no system can currently answer at all. These gaps matter more than failures, because a failed control is visible while a requirement with no data source produces a narrative that passes. The claim is untested.
Theory
The note's claim, a hypothesis, is that judgment is the scarce part of governance, risk and compliance work, because evidence collection takes the hours that decisions need. When collecting and formatting evidence takes most GRC hours, little time remains for decisions. Automating the clerical work may give that time back.
Pattern
The note recommends measuring the time between response steps rather than counting incidents, because intervals can be generated on demand and compared quarter to quarter, which incident counts cannot. Incident counts depend on how hard an organisation looks. Detection, containment, and recovery intervals can be generated on demand and compared over time.
Theory
Origin-bound, hardware-backed authentication removes a whole class of failure regardless of how convincing the message was. This is the clearest available example of design beating vigilance.
Pattern
Where a platform enforces a setting, produce the written policy from that configuration. Then the rule and the document cannot drift apart. Keep the enforced rule as the source of record, mark policy without enforcement as unenforced, and report how many policy statements are actually enforced.
Theory
Generated, varied, current scenarios delivered continuously and measured behaviourally are a plausible substitute for a yearly module. Plausible is not proven. Three things would need to be true, and all are testable: simulation measures predict real behaviour, simulation does not damage reporting culture, and scenarios stay within ethical and employment boundaries.
Theory
Certification scope is negotiated. A clean report describes the environment that was examined against the controls that were selected, at the time of the examination.
Theory
A restore can return all the data and still come too late. Time, sequence, and hidden dependencies often cause the loss. Restore order, recovery credentials, network capacity, and staff availability do not appear in a backup report, but all of them appear in a timed drill.
Theory
The note's observation is that a security purchase is judged on deployment, not on evidence that the tool changes an attack outcome. The fix is to add a named production test as an acceptance condition. Procurement produces a deployment date. Nothing in the ordinary purchase process produces evidence that the tool changes an attack outcome in this environment.
Theory
If nobody can show that a control works, score it as failing. Amber and blank let an untested control sit quietly beside a tested one.
Theory
The note recommends assessing what a compromised vendor's own access could reach, not only whether the vendor protects your data, and how you would sever that access without the vendor's cooperation. Third-party risk programs assess whether a vendor protects your data. They rarely assess the blast radius of the vendor's own access to your systems.
Theory
The chain from clinical need to post-market observation should be current every day, not rebuilt in the weeks before a submission or an audit. Reconstruction is where the errors enter.
Pattern
One ranked stream of judgment calls, each carrying a recommendation, calibrated confidence, reasoning, evidence, the policy in force, the downside if wrong, the alternatives considered, a deadline and the role required to authorize it.
Pattern
A flight recorder for every recommendation and action: what happened, who initiated it, what data was used, which policy and model version were in force, what a human changed on review, and whether it was later judged helpful, neutral or harmful.
Pattern
Autonomy is granted per workflow across four levels, from observe to operate within policy, against measured shadow-mode agreement, with drift monitoring and a rollback path. A single global autonomy score is unsafe.
Theory
Import, reconcile, parallel run, readiness score. What cannot be reconciled is listed individually rather than rounded away, and shadow-mode disagreement clusters reveal where the operation is unready before anyone cuts over.
Pattern
Billing readiness presented exception-first: what is ready, what is blocked and why, what conflicts with policy, and what is documented but should not be billed. The system never asserts final eligibility and never submits a claim.
Pattern
Clustered groups of patients and a conversational explorer replace the filter-and-sort grid. Patients are grouped by what they need operationally, and the grouping itself can be interrogated.
Pattern
The regulated development system, described as work rather than paperwork: research, drafting, traceability, orchestration, evidence management, and audit support, with qualified professionals holding every judgment and approval.
Pattern
Find the reimbursed problem before designing anything. Coverage, coding, payment, and utilization are public, so whether anyone will pay is a research question with a documented answer, not a bet taken after two years of engineering.
Pattern
Enrollment changes, staff departures, program shifts, cadence and threshold changes and autonomy increases are run against the operation before they are made, with assumptions, uncertainty and risks shown rather than a single number.
Pattern
The home screen is a narrative of what changed since the last review: what the system handled, what failed, ranked developments, one intervention worth making, and an evidence link on every claim.
Theory
Do not design bespoke electronics unless a commodity part is demonstrably inadequate for the claim being made. The burden of proof sits with the custom design, the same way Zero Neo puts it on new software.
Theory
Tile walls, module sidebars and worklists are the visible residue of software that could not reason. Zero dashboard is not a visual preference; it is what an interface looks like once the ranking moves inside the system.
Pattern
Leadership reporting written as prose that states the causal claim, with measures, believed drivers and confidence in support, and an explicit section on what remains unknown.
Theory
A rules-based operation has no mechanism to break the link between panel size and headcount. An AI-native one does, but the first two quarters of a migration cost more, not less, and the curve only bends where shadow-mode agreement supports widening autonomy.
Pattern
A narrative generated around the question currently being asked, with timeline lanes that draw missing data as missing, and explicit reasoning about which care program actually fits.
Pattern
Architectures where a smartphone or wearable is a component of the medical device, not a companion screen. It removes hardware and adds obligations, and the trade is only worth making with both sides written down.
Pattern
Every statement the system makes carries a type: observation, inference, recommendation, automated action, human-approved action, unresolved uncertainty, or prohibited action. Missing data is rendered as missing, and standing constraints hold at every autonomy level.
Pattern
Separate component availability from medical performance. The part being cheap says nothing about calibration, accuracy, reliability, safety, cybersecurity, manufacturing controls, or evidence. Confusing the two is how consumer-grade thinking hurts patients.
Theory
No proven outcome improvement without a connected analytics warehouse; disagreement concentrating in recent medication changes; projections that remain projections. The limits stated plainly, in one place.
Theory
The rejection criteria, written before we get attached to anything. Novel materials, exotic sensing physics, sterile manufacturing, life-sustaining risk, and trial-scale evidence requirements all put a category outside this thesis.
Theory
This note shows how to estimate how long adoption will take, so a reader can plan around institutional clocks instead of assuming they disappear. The estimate covers three points: first use, repeat use, and routine use, with the source, range and confidence attached to each. Estimate the time from first evidence to first use, repeat use, and routine use without pretending institutional clocks disappear.
Pattern
Give a capable future competitor the customer outcome and ask for credible routes around the proposed boundary. This report shows whether the boundary holds: each route is ranked by how much penalty it carries, so a reader sees which boundaries are real and which a rival can walk around cheaply.
Theory
Specialized SaaS won largely because configuring general-purpose platforms was expensive. If AI collapses that cost, the reason for the historical result stops applying. This note sets out that hypothesis, states what is being measured to test it, and names the parts that stay hard.
Pattern
This note gives a test for how much of an asset's claimed advantage survives when AI makes ordinary reasoning and software cheap, so a reader can see which advantages disappear and which remain. It is a scenario test, not a forecast. Assume capable AI makes ordinary reasoning and software cheap, then identify how much of the claimed advantage disappears.
Theory
Test what remains scarce after a competitor gains better models, tools, and engineering capacity. The score reviews dimensions such as proprietary data, legal rights, and workflow control, supports each score with a source and contrary case, and rejects resilience that depends only on today's model weakness.
Pattern
This note gives a way to see which rights a product wedge already has and which it still lacks, so gaps surface before a build, sale or license decision. It is an issue map for qualified review, not a freedom-to-operate opinion. Map the rights owned and the rights still needed to build, sell, deploy, manufacture, distribute, or license a product wedge.
Pattern
Match each scarce asset to the narrowest control that can protect and commercialize it. This memo helps a reader choose among patent, secret, contract, license and other rights, so the firm acquires a right only when it has a commercial job, not because the right is available.
Pattern
Represent trust as evidence about a narrow capability, approved sources, authority, incidents, and recertification. An AI credential is a task specific operating record that can be narrowed, suspended, or renewed as evidence changes. It is not a professional license or legal credential.
Pattern
This note sets a rule for granting and withdrawing a worker's authority: evidence earns more authority, and a material change in model, source, policy, population, workflow or incident cuts it until retesting is complete. It matters because strong performance alone does not justify wider authority. Increase authority only after evidence and reduce it automatically when material conditions change.
Pattern
Show who requires work, who performs it, who pays, who benefits, who waits, and who can change it. The matrix exposes cost shifting and the party able to remove the cause, but it does not settle the policy choice, because different parties may have sound reasons for the same work.
Theory
The note finds that a business's application collection is nobody's design or responsibility, and that it should be reconciled on a schedule the way clinicians reconcile medications. Applications accumulate the way medications do. Each addition was reasonable at the time; the collection is nobody's deliberate design and nobody's responsibility to review.
Pattern
Identify which repeated work creates future judgment and replace that learning path before automation removes it. This map matters because automating routine work can strip future workers of the cases and feedback they need to become competent. It preserves the learning, not the burden.
Pattern
Test whether patient access, workflow control, payment, outcomes, technology absorption, and learning support a care business. The screen scores each dimension with evidence, keeps any fatal weakness visible, and ends in a decision to build, acquire, partner, license, monitor, or stop.
Pattern
This note decides readiness by the slowest essential condition: a product is not ready for routine care because its technical component is ready. The map organizes the review but does not establish clinical safety, regulatory standing, coverage, or professional approval. A review of patient, caregiver, clinician, site, supply, data, payment, and exception readiness before an intervention enters routine care.
Pattern
Bring the hypothesis, evidence, economics, rights, uncertainty, failure case, and next decision into one reviewable record. The package lets a reviewer decide on a care model with every material claim and every missing answer in view, instead of an average that hides a fatal weakness.
Pattern
Choose enough comparison to tell whether a recomposed workflow caused the claimed change. The plan matches the study design to the claim and narrows the claim when the design cannot distinguish the intervention from staffing, case mix, policy, or season, because operational acceptance and causal effect answer different questions.
Pattern
This note says to pick the smallest observable test that could reverse the decision, and to prefer behavior over interest. A reader gains a cheaper way to settle the assumption that matters most, and no larger experiment should be funded when a smaller one can invalidate it. Reduce the most important uncertainty with the least time, money, access, and patient exposure reasonably required.
Pattern
Translate a claim or technical principle into a current workflow, buyer, product wedge, and demand experiment. The map turns an abstract claim into the smallest test of whether another party will commit money, data, access, time, or workflow change. It does not establish claim coverage or product demand.
Pattern
Plan customer learning, demonstrations, and publication without casually surrendering useful options. The checklist places a review before pilots, demos, papers, repositories, and public launches, and favors outcome, problem, and workflow questions that need little technical disclosure. Counsel should decide disclosure and filing consequences.
Pattern
This note gives a memo format that ends in one chosen mode, one fallback, a first experiment, an owner and a decision date. It matters because patentability alone is not a reason to form a company, and past importance is not a reason to keep a patent. Force competing cases for building, attaching, licensing, selling, holding, opening, or abandoning an asset.
Pattern
Trace customer value to the smallest constraint a capable rival cannot remove without losing that value. The map identifies the narrowest constraint that survives credible alternatives and better AI, so a boundary rests on what the customer buys and not on an element a rival can replace without penalty.
Pattern
Mark every competitor claim as observed, disclosed, reported, or inferred, so analysis built on it cannot quietly promote a guess. Labelled claims let an engine say when a recommendation rests on inference rather than evidence, and contradictions between credible sources are kept as findings.
Pattern
This note gives a way to measure how much credentialed time, authority and liability a workflow uses per accepted outcome, before and after a redesign. Lower exposure is not automatically better, so the redesign stops when accepted outcomes, responsibility, trust or capability formation worsen. Count where credentialed time, authority, supervision, and liability enter one accepted outcome.
Theory
Training, credential, licence, supervision, and liability cover exist as a stack because each layer is insufficient alone. An AI worker arrives with none of them.
Pattern
Compare spending, science, translation, delivery, policy, rights, and commercial movement without hiding confidence. The scorecard records measure, source, confidence, and contrary evidence for each dimension, and a high composite score cannot repair a missing provider base, payment route, workflow owner, or credible mechanism.
Pattern
This note gives a log that ties customer behavior to claim, continuation, filing and maintenance decisions, so rights follow evidence. Data access, implementation, payment and repeat use count for more than interviews and complaints, and one loud request is not enough to redirect rights. Keep customer behavior connected to claim, continuation, filing, and maintenance choices.
Pattern
Enough reflection of an account that anyone can prepare before acting, bounded by confidentiality terms, privacy obligations, and contractual restrictions. The customer Eidolon is useful only if restricted material is decided and held separately before writing, because a reflection that keeps material the company had no right to retain is a liability.
Pattern
Most assembled systems fail before any model runs, because the data they depend on is incomplete, inconsistent, or somewhere nobody checked. Before a workflow is a candidate for automation, answer four questions in writing: availability, quality, gaps, and alignment. Repair the data substrate first.
Pattern
This note finds that case accuracy does not predict population harm from a shared fault, so scaling should stop when one untested dependency can affect more outcomes than the organization can detect, contain and recover. The map gives the concentration and blast radius thresholds to check. Show which workers share models, sources, policies, tools, identities, vendors, and people so one fault cannot spread unseen.
Pattern
Make stale, weak, unsupported, single-source, and unresolved claims visible before they quietly drive decisions. The register records each claim's evidence status, risk if wrong, owner, and decision blocked, so debt that can reverse a clinical, economic, rights, or adoption decision is resolved first.
Pattern
This note gives a register that sets a useful life, refresh schedule and decision trigger for each public signal, so stale evidence does not drive current decisions. Stale evidence remains in the historical record but loses authority over current decisions. Set the useful life, refresh schedule, and decision trigger for every public signal used in active research.
Theory
Rank evidence by the scarce real-world commitment it reflects, from public signal through replicated outcome. The ladder lets a reader state which rung supports each claim and what next commitment would materially change confidence, instead of treating all evidence as equal.
Pattern
Keep every consequential operational claim connected to its source, custodian, transformations, and useful life. The result is an evidence chain a reviewer can follow in both directions, from the real event to every derived field and decision. Provenance shows where a claim came from, not that the source is correct.
Pattern
This note decides where to work on a regulated intervention: on the failure mechanism that limits the outcome and can be changed. It classifies failures and traces each one to a measure, a responsible party and a smallest test, and stops when the mechanism is weak, immaterial or beyond practical control. Locate where a regulated intervention fails, what can be measured, and which party can change the binding condition.
Theory
This note gives a matrix for judging whether a particular operator makes an underused asset practical, using a bounded research or customer task before any company or transfer is discussed. A match based only on title, biography, enthusiasm or a general industry connection is rejected. Test whether an operator's knowledge, access, data, rights, and timing make an underused asset more practical.
Pattern
Businesses do not need CRM software; they need work performed. Decompose the outcome into roles, tasks, workflow, and capabilities, and the application stops being the organizing unit.
Pattern
Automation follows understanding. Work becomes explicit, then observable, then repeatable, and only then is it a candidate for AI execution with human exception handling. Skipping a stage does not speed the sequence; it moves the failure later, where it costs more.
Pattern
Define how consequential work continues or stops when AI, data, tools, identity, or outside services are unavailable or untrusted. The plan sets modes from normal operation to safe stop, and a fallback counts only once it has been exercised. Deployment stops when the operation cannot fail safely.
Pattern
List every independent condition that must hold for an intervention to reach repeatable use. The map names the current state, evidence, owner, and stop rule for each condition, and identifies the binding condition that sets the adoption clock, which is where work should concentrate.
Pattern
This note decides when a pilot may advance: only when an operating owner accepts the work and repeat use survives beyond the sponsor. It maps stakeholders and tests activation, voluntary use and abandonment, so a reader can separate sponsored use from routine institutional use. Map the people, evidence, approvals, work, and support needed to move from sponsored pilot to routine institutional use.
Theory
The published evidence that fragmented, poorly usable software has measurable costs in healthcare, what it supports, and what it does not. The evidence establishes a cost and locates the defect between applications. It does not show that consolidation fixes it, so the note serves as context for the Zero Neo hypothesis, not proof.
Pattern
Test whether important use can be observed and evidenced without assuming access to a competitor's private systems. The review places each material element on a spectrum from publicly observable to effectively hidden and records commercial importance, evidence difficulty, and questions for counsel. It is not a claim chart or infringement conclusion.
Pattern
This note gives a reviewable chronology that connects each material choice to the evidence and person responsible, and that can be handed to counsel and diligence teams. The record does not determine inventorship or ownership. Keep a dated record of human insight, source material, AI assistance, experiments, decisions, and claimed contribution.
Pattern
Make work inspectable, assignable, testable, versioned, and governable before attempting broad automation. The pattern turns observed work into Work Units and Worker Contracts that can be tested in shadow mode and versioned, and it stops when specification adds more burden than clarity.
Pattern
The reference implementation of the closed loop: make a knowledge-sharing request explicit, observable, and answerable, so delivery, consumption, comprehension, application, and outcome stay separate claims with separate evidence.
Pattern
Separate who creates, controls, authorizes, owns, transfers, and finances risk at each stage. The map gives a stage by stage view of risk and responsibility with unresolved questions, and a recomposition is rejected when no party clearly owns a consequential failure. Technical architecture does not establish legal liability.
Pattern
The smallest institutional reflection that changes AI output: what the company does, how it is organised, who decides, what it sells, and what it will not claim.
Pattern
Find where a person's or organization's unusual capability materially changes an accepted outcome. The map tests whether the difference survives comparison with peers, tools, and AI, so the firm rejects the claim when ordinary peers reproduce the result. Native Alpha™ is a hypothesis, not praise.
Theory
Concentrate research and protection where unusual insight, customer importance, resistance, and compounding are strongest. Strategic value is unevenly distributed across a product's components, so the review scores each element and ranks attention. It is not a valuation, patentability test, or legal conclusion.
Theory
This note gives a review for judging whether a redesign of work raised Native Alpha™ density and improved the outcome. It is a qualified view, not a universal numerical score, and the redesign is rejected when density rises on paper but outcomes, learning, trust or resilience worsen. Test whether scarce capacity is moving toward work where unusual capability changes or compounds the result.
Pattern
Recover the unusual observation and technical principle before drafting turns the conversation toward an implementation. The interview produces a dated Native Alpha™ thesis with open questions and a next step. It does not establish inventorship, ownership, patentability, or demand, which go to specialists.
Pattern
Read a patent family backward to recover the insight, present scarcity, and possible modern use. The output is a sourced commercial thesis with alternative explanations and a next test, and a claim summary must not be turned into a story about inventor intent without evidence.
Pattern
This note gives a ledger of failed approaches, so the cost of a failure is not paid again when a person or project leaves. It records the conditions that make each approach fail and what design decision the lesson changes, and it keeps evidence and uncertainty attached rather than folklore. Preserve failed approaches and the conditions that make them fail before the lesson leaves with a person or project.
Pattern
Decide which layers should be open, standardized, licensed, proprietary, secret, or patent protected. The map gives a reason for each layer and names the right, duty, owner, field, and exit path for every closed one, so a commodity layer is not closed when control costs more than it returns.
Pattern
Trace an operational claim to independent evidence and distinguish intended, reported, recorded, inferred, observed, and verified state. The output is a queryable evidence chain and the gap between reported and observed state. A complete record can still be false, and Operational Truth™ does not prove causality.
Theory
This note gives a test for whether a redesigned care pathway lets its owner keep the value it creates. It rejects the theory when labor remains proportional, outcomes are not measurable, payment does not reward the change, or suppliers retain the decisive bargaining power. Test whether a redesigned care pathway can retain value created through lower cost, better outcomes, or changed risk.
Pattern
Test whether the intended real world result occurred within stated quality, safety, time, cost, and evidence limits. Acceptance is a continuous record tied to worker and workflow versions, and authority is reduced or stopped when thresholds fail. Passing an outcome test does not prove the worker caused the outcome.
Pattern
Start by preparing evidence for a person, then grant narrow action only after review data supports it. Authority is promoted one level at a time, from observing to independent execution, using error, edit, escalation, and incident evidence. Some work should never progress beyond advice or packet preparation.
Pattern
This note gives a before and after map of the unpaid work patients and caregivers do, so it counts in the economic and human result. A workflow improvement that merely exports more work to patients or caregivers than it removes is rejected. Count unpaid calls, forms, portals, travel, record gathering, repeated explanations, and home work around care.
Pattern
When one reflection links to another, decide what a reader inherits, what it must request, and what it may never see. Permission has to travel with the link, or a worker cleared for one Eidolon can read every executive, customer, and system Eidolon it references.
Pattern
Keep a role specification and a person's Eidolon as separate linked objects so work is not written for an office as though it were a personality.
Pattern
Treat the owned platform as a substrate of capabilities rather than a bundle of products, then map those capabilities against the jobs that category software is bought to perform.
Pattern
This note gives a one-review packet that ends in a decision with an owner, action, budget, due date and reversing evidence. A packet without a decision is reference material, not portfolio management, so the next commercial action is named in the packet itself. Put rights, customer value, evidence, cost, observability, and the next commercial action in one review.
Pattern
Choose how to handle a claimed differentiated capability after testing what makes it valuable. The four choices are preserve, amplify, encode, or reject, and they can coexist across parts of one capability. Encoding stops when it weakens trust, learning, control, portability, or the advantage itself.
Theory
Judge a reflection by the work it improves. Add one fact, rerun the task, and keep the fact only if the accepted outcome gets better.
Theory
Facts age at different speeds. Date them, give the fast ones a review interval, and treat an unreviewed reflection as an unknown rather than a truth.
Pattern
Connect conditions, populations, spending, providers, evidence, products, payment, rights, pathways, and commercial activity. Each edge states why two records are connected, the time period, and confidence. The graph is for finding mismatches and changes and generating hypotheses, not automatic commercial conclusions.
Pattern
This note finds that a public signal can justify investigation but is not a validated opportunity until external commitment or real-world evidence supports it. The ledger keeps sourced observations separate from calculations, interpretations, AI inferences, hypotheses and commercial claims. Keep sourced observations separate from calculations, interpretations, AI inferences, hypotheses, and commercial claims.
Theory
The realistic outcome is not fewer credentialed people. It is credentialed people supervising a distributed set of workers, human and otherwise. The role is recomposed, not deleted, and how many workers one person can oversee is the unknown that decides whether the economics work.
Pattern
Track ownership and permitted use of know how, data, worker contracts, prompts, tests, evidence, and operating records. The resulting rights record can block release when a material asset is unresolved, and it supports qualified legal review without deciding ownership or enforceability.
Pattern
This note gives a map of who carries each risk and who controls it, with the rule that responsibility should not move away from control. It matters because a party asked to carry risk needs the information, authority and intervention path to manage it. Show who carries clinical, product, data, implementation, cybersecurity, financial, operational, and reputational risk.
Theory
Review where scarcity sat, where it sits now, and which change will move it next. The review ends in a decision to protect, test, move effort, open a layer, license, sell, maintain, or stop. A date without a named change and evidence is guesswork, not an asset half-life.
Pattern
This note gives a rule for the build, buy, license, partner or consume choice: own a component when control changes the outcome, defensibility, safety, financeability or ability to learn, and consume it when it is interchangeable and dependence is manageable. Choose whether a care organization should build, buy, license, partner for, or consume a technical component.
Theory
A role name hides the scope, authority, evidence, exceptions, and outcomes that determine whether work can move. Comparing the formal description with actual tasks and decisions yields a role decomposition into distinct work units. A title can stay useful for employment, identity, and accountability even when it is a poor automation unit.
Pattern
State what a worker may do, what evidence it must use, when a person reviews it, and how it fails safely. The contract is versioned so it survives a change of model or vendor. It governs the worker but grants no legal authority the organization lacks, and deployment stops when ownership or failure behavior cannot be stated.
Theory
New business-operations software should be the last resort. Start with the capabilities already owned and move outward only when evidence shows a real gap. The principle reverses the burden of proof: the proposer must show why the outcome cannot be achieved with what the business already owns.
Pattern
This note gives a record that makes an adaptive treatment sequence testable, stage by stage, so a reader can check whether sequence or timing changes the outcome. The record supports workflow research and does not prescribe care. Specify the measurements, transitions, timing, decisions, and exceptions in an adaptive treatment sequence.
Pattern
Move from the current operation through shadow work and narrow authority while keeping rollback available. The plan stages the move with gates, costs, owners, and fallback, and reports time to net positive value, because steady state savings do not erase transition cost or temporary risk.
Theory
Test whether a composite readiness measure can improve treatment timing or selection without hiding weak dimensions. The index is rejected when aggregation hides a fatal condition, the score cannot guide action, or performance does not transfer across settings, and it must show that acting on the score improves outcomes.
Theory
The conditions under which specialized software remains the right answer, stated precisely enough to be used in an actual review. Where requirements are certified, regulated, or deep in domain logic, Zero Neo has no claim and the hypothesis is treated as rejected. New software is the last resort, and sometimes that is where a case ends up.
Pattern
Find whether work serves the outcome or was created by a rule, incentive, boundary, or information failure. Each burden is classified and given a disposition of retain, assist, automate, redesign, renegotiate, or remove. Institutional friction can be protective, so classification does not prove a burden is waste.
Pattern
This note gives a versioned record that another person can inspect and test, so a piece of work is described by evidence and not by intended process. A description of intended process is not evidence of actual work, and the unit should be neither too broad to observe nor too narrow to own a result. Describe one piece of work by its purpose, evidence, authority, risk, handoffs, and accepted outcome.
Pattern
Assign work across people, AI, rules, software, systems, devices, services, and governance as one operation. The map gives every Work Unit an owner and every handoff in writing, and it stops when a task saving raises end to end cost, delay, risk, or review burden.
Theory
Subscription price is the easiest number to compare and the least decisive. The hypothesis stands or falls on total operating cost, including the costs of assembling badly.
Pattern
Systems of record at the bottom, platform capabilities above them, AI orchestration above that, then workflows, then the mixed workforce, with observable outcomes at the top and purchased software entering only from the side.
Theory
The larger effect may be in organizations that do have IT. Governing a few strategic platforms is a different job from administering hundreds of applications and the integrations between them.
Theory
Small businesses historically chose between buying SaaS and hiring consultants. If AI can configure owned platforms, a third option appears for organizations that never had one.