Silhouette of Lord Shiva seated in meditation
AMNAYA

SUSTENANCE IS EMPOWERMENT

AMNAYA

HOW IDEAS TAKE SHAPE / THE OPERATING FRAMEWORK

The first 100 days.

A question becomes a test. A test produces evidence. Evidence earns the next commitment.

Fifteen defined sprints, seven decision gates and one accountable record. Configure the dates, territory, sector, targets and risk assumptions before adapting the plan to an Amnaya project.

Download this section · 2-page PDF ↓

01 / SET THE MANDATE

One framework.
Different operating realities.

The inputs below drive the calendar, task quantities, budgets, gates and risk model. These are session-only drafts. Export to keep your work; use the private team workspace for confidential records.

Accountability and incident-response parameters

Calendar days include weekends. Workday counts exclude weekends only; add local holidays and statutory clocks when a project mandate is approved. Currency selection labels amounts and does not convert them.

Download this section · 7-page PDF ↓

02 / THE WORK, DAY BY DAY

A calendar you can interrogate.

Review the daily evidence at 16:00 and each seven-day sprint at 17:00 in the selected project time zone. Formal gates close at 18:00 on the dates below. These are proposed review times, not meeting invitations.

View all 45 task windows, dependencies and acceptance tests
Long-cycle projects get a bounded first cycle. For energy, this may be an investment-ready feasibility package; for food, a validated development brief; for healthcare, an authorised workflow simulation. Construction, product sale, patient care and regulatory approval require their own permissions and timelines.

Download this section · 3-page PDF ↓

03 / COMMITMENT MUST BE EARNED

Seven decisions.
Explicit stop conditions.

Proceed, revise, hold or stop. A checked task is a draft assertion. A gate is approved only when an authorised owner accepts the evidence, conflicts and remaining exposure.

Decision rights

Data Centres / evidence

Own source quality, denominators, the baseline, contradictory observations and reproducibility. Challenge unsupported claims.

Centre of Excellence / review

Own methods, policy applicability, safety, conflicts, independent challenge and acceptance criteria. Escalate material exceptions.

Venture Laboratory / execution

Own the work package, resources, instrumentation, corrective action and handover. An authorised owner releases the next commitment.

Download this section · 2-page PDF ↓

04 / KNOW WHAT THE NUMBERS MEAN

Targets are not control limits.

A process can be stable and still miss its target. Track both the quality of the result and the reliability of the process. The demonstration data below is synthetic and reports no Amnaya project performance.

Control-chart workbench

SYNTHETIC DEMONSTRATION

Edit observations / inspect the data contract

Each line contains inspected units, defective units, and one individual cycle time in hours. Defects are binary at the unit level. The cycle-time value must be a single independent measurement, not a subgroup average. Do not mix products, definitions or shifts without stratifying the data.

p-chart · fraction nonconforming

Individuals chart · cycle time

Observed seriesThree-sigma limitsBusiness targetShaded area: baseline

Methods, assumptions and interpretation

p-chart: the pooled baseline rate is total baseline defective units divided by total inspected units. Limits vary with each observation’s sample size and are clipped to 0–100%. It assumes a consistent binary definition and independent units.

Individuals chart: baseline mean ± 3 × average successive moving range ÷ 1.128. Time observations must be independent and comparable. Highly skewed or autocorrelated data needs a different or transformed model.

The first 20 observations are an editable, provisional baseline choice for this framework, not a universal minimum or proof of stability. Baseline signals, sparse counts or zero variation require specialist review. Only points outside the three-sigma limits are flagged here; run, trend and multiple-testing rules are not implemented. Never reset limits simply to conceal an adverse signal.

Methods: NIST proportions charts ↗ · NIST individuals charts ↗

05 / PRICE THE EXPOSURE, NOT A STEREOTYPE

What instability would cost the plan.

A territory’s country-risk estimate, a project’s expected loss and a commercial contingency are different quantities. Enter a dated basis for each exposure. No country rating, sovereign fee or Amnaya surcharge is asserted by the default numbers.

Scenario factors change probability (capped at 100%), delay days and funding spread only. Severity, recoverability, capital, budget, daily cost and quoted mitigation cost stay fixed.

Calculation, pricing discipline and the approval record

Event allowance = exposed capital × cycle probability × loss severity × (1 − recoverable share). Delay allowance = incremental delay days × incremental daily cost. Funding carry = funded exposure × additional annual spread ÷ 10,000 × 100 ÷ 365. Add the separately quoted mitigation cost. Proposed price = (base cost + these allowances) ÷ (1 − target gross margin).

This is a transparent planning convention, not a bank quote, WACC model or compulsory territorial tariff. Recoverability depends on an enforceable contract or policy, exclusions, limits, deductibles and claim timing. No protection is assumed from a premium alone. Delay and event-loss scopes must not overlap; the annual spread must exclude expected losses already charged elsewhere.

Before a quote or investment decision: record event scope, exposure period, low/base/stress basis, currency, local legal review, counterparty terms, funding/insurance quotations, residual exposure, approver, review date and why no loss is counted twice. A higher price cannot make an unlawful or unsafe activity permissible.

Country equity-risk reference: NYU Stern country spreads and premia ↗. Its annual equity estimates are a reference for investment-return analysis, not an input automatically added to this commercial allowance. Risk-transfer reference: World Bank political-risk insurance ↗.

Territory

Transfer restrictions, public-counterparty conduct, political violence, enforceability, site access and changes in rules. Define the actual exposure and credible evidence; do not treat nationality as a risk score.

Sector

Grid access, food safety, product classification, clinical permissions, chemical restrictions or traceability. Sector restrictions may create a stop condition, not a price adjustment.

Project & contract

Counterparty quality, concentration, currency mismatch, payment timing, logistics, scope changes and claims recovery. Separate diversifiable operating uncertainty from country-wide exposure.

Download this section · 3-page PDF ↓

06 / POLICY IS PART OF THE CRITICAL PATH

Three layers.
One applicability register.

Company standards, territorial requirements and sector obligations must agree before live activity. The references below identify questions to resolve; they do not certify that a project is licensed or compliant.

Amnaya source basis. The AMNAYA Founder Governance Code was located in company OneDrive records and reviewed on 5 November 2026. Its themes include integrity, scientific rigour, accountability, confidentiality and long-term stewardship. Entity adoption, signed approvals, operative versions and effective dates have not been independently confirmed. The document’s private text is not republished here.

Explore the proposed P01–P16 policy framework ↗

The proposed policy set complements the applicability register; neither a draft nor an export constitutes entity adoption.

The fields every project policy record needs

Policy ID · issuing body · entity/site/product/activity · territory and local authority · source clause and version · effective/commencement date · applicability reasoning · accountable owner · independent reviewer · renewal/expiry date · evidence reference · exceptions · next review. Confirm whether a rule is proposed, enacted, commenced, superseded or locally adopted.

Framework references checked 5 November 2026. A later project review must verify current law and local applicability. “Draft evidence supplied” is a planning status, not an owner sign-off. Unresolved critical obligations hold live-pilot Gate 56 and the final Gate 100.

Download this section · 3-page PDF ↓

07 / MAKE FAILURE VISIBLE EARLY

Errors, biases and
the response they demand.

These are prospective failure modes, not an incident history. Scores are illustrative triage parameters: severity × likelihood × difficulty of detection, each from 1 to 5. A severe safety or legal issue overrides the score.

Download this section · 2-page PDF ↓

08 / PROVE WHAT CHANGED

Accomplishments need receipts.

A planned output, a task check and an independently accepted result are separate records. Project-specific achievements start unverified. None of the demonstration charts, risk prices or targets establishes an accomplishment.

A project accomplishment submitted for review

This workbench does not certify or publish your entries. The export retains the status “submitted for owner review.” Keep confidential evidence in the private document vault; do not upload it to this public page.

THE DAY-100 DELIVERABLE

A defensible next decision.

A maintained evidence pack, a measured pilot or feasibility result, the policy position, residual risks, an approved next-stage budget and an accountable owner. Proceed, revise, hold or stop according to what the evidence supports.

Continue in the private workspace ↗

Exports are working drafts. They do not overwrite team records or create approvals. Reloading this page clears session drafts unless you export them.