// DEMIURGE — MANIFESTO (/manifesto)
const Manifesto = () => (
  <React.Fragment>
    <a href="#main" className="lp-skip">Skip to content</a>
    <div className="lp-starfield" aria-hidden="true"></div>
    <div className="lp-vignette" aria-hidden="true"></div>
    <SiteNav/>
    <main id="main" className="page-wrap">
      <section className="page-hero">
        <div className="lp">
          <div className="lp-eyebrow">/ Manifesto</div>
          <h1 className="page-h1">Software should do the work — <em className="lp-brass">not perform it</em>.</h1>
          <p className="page-lede">
            Demiurge Systems exists to deploy digital operators that carry real operational weight:
            answering calls, booking meetings, chasing leads, and running the back-office — with a human
            holding the wheel. Not demos. Not dashboards that describe work. Systems that do it.
          </p>
        </div>
      </section>
      <section className="page-body">
        <div className="lp">
          <div className="prose">
            <h2>Our purpose</h2>
            <p>
              Most “AI” a business encounters is theatre — a convincing surface with nothing behind it that
              survives contact with a real Tuesday. We build the opposite: operators that are wired into the
              tools a business already runs on, measured by outcomes it can feel — meetings on the calendar,
              calls answered, hours returned.
            </p>

            <h2>Operational AI, not intelligent-sounding AI</h2>
            <p>
              An operator is a narrow, accountable worker with a defined job, real inputs, real outputs, and a
              clear boundary around what it may do on its own. We prefer a small system that reliably does one
              valuable thing to a sprawling one that impressively does nothing. Intelligence is judged by work
              completed, not by how the output reads.
            </p>

            <h2>Human oversight and accountability</h2>
            <p>
              Autonomy is earned and bounded. Every operator has explicit limits on the actions it can take
              unsupervised; anything consequential — spending money, sending on your behalf, changing records
              of record — is designed to surface for human review. A named human is always accountable for what
              an operator does. We build the off-switch before we build the automation.
            </p>

            <h2>Systems that ship production-capable</h2>
            <p>
              A deliverable is not done when it looks finished — it is done when it runs, in production, under
              real load, and a customer can depend on it. We hold ourselves to the boring virtues that make
              that true: security, privacy, accessibility, maintainability, and clean deployment. If it cannot
              be operated after we hand it over, we have not delivered.
            </p>

            <h2>What we refuse to do</h2>
            <ul>
              <li>Ship a demo dressed as a product, or a claim we cannot evidence.</li>
              <li>Let an operator take irreversible action without a human in the loop.</li>
              <li>Hoard the keys — customers should receive systems they can actually run and own.</li>
              <li>Fabricate compliance, certifications, or numbers to close a deal.</li>
            </ul>

            <h2>Responsible automation</h2>
            <p>
              We treat automation as a scalpel, not a firehose. The right amount of autonomy is the most that
              can be granted without moving a decision that a human should own out of human hands. When in
              doubt, we constrain the system and tell you exactly where its edges are.
            </p>

            <div className="note info">
              This is the standard we hold our own work to. If something we deliver falls short of it, that is a
              bug — tell us, and we fix it.
            </div>

            <h2>Work with us on it</h2>
            <p>
              If this is the way you want your operations built, <a href="/contact">book a strategy call</a>,
              see the <a href="/packages">packages</a>, or — if you build systems this way too — read
              <a href="/operators"> Operators Wanted</a>.
            </p>
          </div>
        </div>
      </section>
    </main>
    <SiteFooter/>
  </React.Fragment>
);
ReactDOM.createRoot(document.getElementById('root')).render(<Manifesto/>);