Railbase

Product & Suite Subscription Agreement

Version: 2.3 Effective date: 29 August 2026

This Product & Suite Subscription Agreement ("Agreement") is a binding agreement between you ("you", "Customer") and Silkway Tech LLC, a Wyoming limited liability company with a mailing address at 5830 E 2nd St, Ste 7000 #30294, Casper, WY 82609, USA ("Company", "we", "us"). It governs each paid Railbase Product you evaluate, subscribe to, install, and use through railbase.app.

This Agreement supplements the Terms of Service (account, ordering, billing, tax, KYC, sanctions, refunds, and the railbase.app control plane) and the Core EULA (the free Railbase core in which Products run). By starting an expressly offered Product trial, purchasing a Product subscription, or installing or using its Components, you agree to this Agreement, including the Suite Schedule that applies to the selected Product Plan. The stable URL and internal document identifier retain the historical name plugin-agreement so earlier links and acceptance evidence remain verifiable; the agreement governed by the current version is Product-first.

1. Product model and definitions

A "Product" is a customer-facing commercial sale unit published by the Company. A Product is either:

  • a "Suite" — an outcome-oriented Product composed of multiple technical Components; or
  • a "Standalone Product" — an explicitly designated Product that delivers independent business value without requiring the Customer to buy a Suite.

A "Product Plan" is the Basic, Pro, Max, or other named variant of a Product shown at checkout. The Product Plan defines the Product's commercial promise, roles, workflows, quotas or limits, and exact Component composition. Basic, Pro, and Max belong to the Product, not to each Component.

A "Component" is a proprietary, licensed Railbase plugin delivered as a signed, encrypted data-resident bundle containing backend logic, schema, declared UI, and manifest. A Component installs into the Customer's Vault and executes only through mediated capabilities of the self-hosted Railbase core. It has no standalone executable, process, port, database, or supported run path outside Railbase. A Component is a technical delivery and entitlement unit, not a separate sale unit unless the Company expressly classifies and publishes it as a Standalone Product.

The Connector Component is integration fabric included only in Products that require governed data movement. Connector is never offered as a Standalone Product and has no separate Product price or subscription.

2. Product subscription license

Subject to your compliance with this Agreement and payment of applicable fees, the Company grants you a non-exclusive, non-transferable, non-sublicensable, revocable license to install and use the subscribed Product through its delivered Components, in encrypted form only, inside your own Railbase instance, for your internal business purposes, for the named company, Product Plan, deployment scope, and subscription term recorded at checkout or in an Order.

The Product subscription is bound to the specific named legal company selected in the Customer Account. Human users, job positions, role assignments, approvers, and viewers are authorization concepts and are not billing meters unless an Order expressly states otherwise. A Product license does not transfer to another legal entity merely because the same Account manages both entities; a supported reassignment requires the controls and approval stated in the Account or Order.

The Product's versioned composition and fingerprint form part of the entitlement snapshot. Each included Component receives the technical entitlement needed to deliver that Product. The Customer does not acquire source code, ownership of a Component, or a right to use a Component outside an active entitlement source.

3. Ordering and the Account-only purchase boundary

Self-service Product acquisition is available only through a signed-in Railbase Account for a named company whose required company-verification/KYC status is approved and whose transaction clears the Terms' payment, sanctions, export, and tax controls. Public Product pages and a self-hosted Railbase console may describe a Product or link to the Customer Account, but they do not originate or authorize a paid charge.

Each self-service Product Plan creates one Product subscription and one Product line with the payment provider. The Product price is the price of the Product outcome and Product Plan; it is not calculated by adding catalogue prices for Components. railbase.app may show a Component breakdown as technical entitlement and accounting detail, including zero-value allocations, without turning a Component into a separately priced SKU.

Checkout blocks a duplicate active subscription for the same Product and named company. A company may subscribe to different Products that contain one or more shared Components. Each Product remains independently priced and billed, and Component overlap does not create a discount, refund, credit, or right to unbundle a Product unless checkout or an Order expressly states otherwise. The control plane retains each Product as a separate entitlement source and composes the effective technical entitlement from all active sources.

The Suite Schedules in this Agreement apply automatically according to the Product purchased. They are part of the same Product subscription contract and do not create a separate Component subscription, SKU, price, agreement, or checkbox. The Account presents one affirmative acceptance for this Agreement and the Terms of Service; its evidence pins the version and hash of this complete document, including the applicable Suite Schedule.

4. Product plans, renewal, plan changes, and cancellation

Unless an Order states otherwise, self-service Product subscriptions are billed monthly per named company and renew automatically until cancelled. Current prices, currency, tax treatment, Product Plan composition, and any expressly offered promotion are shown before confirmation in the Account checkout.

A Product Plan is indivisible. The Customer cannot remove, downgrade, cancel, or price an individual Component within the Product. Changing Basic, Pro, or Max atomically changes the Product's single billing line, declared composition, fingerprint, and Component entitlements.

An upgrade may take effect immediately and produce an immediate prorated charge disclosed through the billing flow. A downgrade may change the Product Plan and technical composition immediately without a refund or credit for the current period; where the Account flow uses no proration, the lower recurring price applies at the next renewal. A removed Component stops executing when no other active Product entitlement source supplies it; retained self-hosted data is not automatically deleted.

Ordinary Customer-requested cancellation schedules the whole Product to stop renewing at the end of the current paid period. The Product and its Component entitlements ordinarily remain available until that boundary. This does not limit an earlier suspension or revocation required by non-payment, full payment reversal, chargeback, breach, sanctions, export controls, account closure, or an adverse enhanced-verification decision under the Terms.

If two active Products supply the same Component, ending one Product removes only that Product's entitlement source. The Component may continue under the other Product's source, but the ended Product's roles, workflows, quotas, and other Product-level rights do not survive.

5. Technical protection, activation, and revocation

You acknowledge and agree that:

  1. Components are encrypted at rest and license-gated at execution and run only while at least one valid entitlement source for the named company is present;
  2. licenses may be device-bound (node-locked) to the Railbase instance that activates them, and moving them may require release or re-pointing through the Account;
  3. Railbase periodically verifies licence state with railbase.app; a connected instance normally applies a suspension on its next heartbeat, while a node-bound token is a rolling validation lease of no more than 24 hours, capped by the commercial term;
  4. the Company may suspend or revoke an affected Product or Component entitlement for non-payment, full payment reversal, chargeback, cancellation at the applicable boundary, breach, sanctions/KYC findings, export restrictions, or misuse; a partial credit note alone does not revoke an otherwise paid entitlement; and
  5. attempting to decrypt, extract, copy, study, modify, or run a Component outside the licensed Railbase core, tamper with enforcement, or share licence credentials outside the licensed organization is a material breach.

6. Restrictions

You may not, and may not permit or assist anyone else to: (a) reverse engineer, decompile, disassemble, decrypt, or derive the source or contents of a Component except to the extent the restriction is prohibited by applicable law; (b) modify or create derivative works of a Product or Component; (c) redistribute, resell, sublicense, rent, lease, or host a Product or Component for third parties; (d) exceed the licensed company, Product Plan, deployment, quota, or usage scope; (e) circumvent entitlement, metering, signature, or execution controls; (f) separate and use a Component as though it were independently purchased; or (g) use a Product or Component in violation of applicable law.

7. Evaluation and internal testing

The free Railbase Core may be evaluated after the Account and company-verification gates described in the EULA. A Product or Standalone Product has a trial only where the Account or Product page expressly offers one. Product trials are time-limited, company-specific, may be limited by account, company, deployment, device, or network, and may be revoked at any time. An internal-testing assignment is invitation-only, is not a commercial purchase, and carries no availability or support commitment.

A Component included in a Product does not acquire a standalone trial merely because it can be installed independently by the runtime. Connector has no standalone trial.

8. Data, dependencies, and third-party services

Products run inside your self-hosted Railbase and store ordinary business data in your Vault. The Company does not ordinarily receive that business data. The core transmits the limited account, company, Product/Component entitlement, deployment, version, activation, and heartbeat metadata described in the Privacy Policy and EULA.

Components may publish and consume declared events through the Railbase event bus and may use core-mediated integrations. One Component's output does not become warranted, verified, or upgraded in status merely because another Component consumes, displays, attaches, or acts on it. The applicable Suite Schedule continues to govern Product output wherever that output is used. You are responsible for compatible configuration, appropriate roles, lawful source access, cross-Component workflows, and third-party services and credentials you configure.

9. Installation, updates, and compatibility

After purchase, the Product appears as an owned Product in Railbase. Installation is initiated from the self-hosted Railbase administration surface. Before installation, railbase.app verifies the Account entitlement, named company, Product, Product Plan, composition fingerprint, exact release-locked Component set, Component versions, and signed artifacts. Railbase then installs each Component through its ordinary protected installation path.

Product and Component updates are delivered only through the Railbase distribution control plane. An update may require a minimum Core version. The Company may change or retire a Product, Product Plan, or Component prospectively. A retired Product remains licensed for the paid term unless otherwise stated, but may stop receiving updates or new sales. Compatibility with future Core versions is not guaranteed beyond commercially reasonable efforts.

10. Ownership

Products, Components, bundles, manifests, documentation, trademarks, and related intellectual property are and remain the exclusive property of the Company and its licensors. They are licensed, not sold. All rights not expressly granted are reserved.

11. Warranty disclaimer

PRODUCTS AND COMPONENTS ARE PROVIDED "AS IS" AND "AS AVAILABLE", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, AND NON-INFRINGEMENT. PRODUCT OR COMPONENT OUTPUT — INCLUDING MACHINE TRANSLATION, ANALYTICS, RISK, COMPLIANCE, CONNECTOR, FINANCIAL, EDUCATION, OR AUDIT CONTENT — IS PROVIDED FOR CUSTOMER EVALUATION AND IS NOT PROFESSIONAL, LEGAL, FINANCIAL, ACCOUNTING, EDUCATIONAL, REGULATORY, OR AUDIT ADVICE. THE APPLICABLE SUITE SCHEDULES STATE ADDITIONAL LIMITATIONS AND OPERATIONAL SAFEGUARDS.

12. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE COMPANY WILL NOT BE LIABLE FOR INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY, OR PUNITIVE DAMAGES, OR LOSS OF PROFITS, REVENUE, DATA, GOODWILL, OR BUSINESS OPPORTUNITY, ARISING FROM OR RELATED TO A PRODUCT OR COMPONENT. THE COMPANY'S TOTAL AGGREGATE LIABILITY UNDER THIS AGREEMENT WILL NOT EXCEED THE AMOUNTS YOU PAID FOR THE PRODUCT GIVING RISE TO THE CLAIM IN THE 12 MONTHS BEFORE THE CLAIM. MANDATORY LAW MAY LIMIT THE APPLICATION OF THIS SECTION.

13. Term and termination

This Agreement applies while you hold a Product subscription, Product trial, or internal-testing assignment. Either party may terminate for the other's material breach not cured within 30 days after notice, except that a breach of Sections 5–6 or a legally required suspension may be acted on immediately.

When a Product or entitlement source ends, affected Components stop executing when no other active source supplies them. Historical records remain in the Customer's Vault under the Customer's retention policy and may become available again after a later compatible subscription. The Customer must export or delete that data through Railbase; the Company cannot do so from railbase.app.

14. Governing law; changes; general

This Agreement is governed by the laws of the State of Wyoming, USA, without regard to conflict-of-laws rules; exclusive venue lies in the state or federal courts located in Wyoming. If any provision is unenforceable, the remainder stays in effect.

The Company may update this Agreement prospectively, including its Suite Schedules. The exact version and hash accepted at checkout are retained as evidence. The accepted version governs that acquisition unless a later version is validly accepted or applicable law requires otherwise. Material changes intended to apply to a later renewal will be notified before that renewal where required.

15. Suite Schedule framework

Each marketed Suite has one Schedule below. The Schedule applies automatically to every Basic, Pro, and Max plan of that Suite; plan-specific clauses apply only when the selected plan includes the described capability. It does not create a second agreement or acceptance. The Customer's obligations continue for retained data, exports, downstream copies, decisions, investigations, educational or financial records, evidence, and reports after suspension, plan change, expiration, or termination.

For every Suite Schedule:

  1. "Source Data" means data, documents, credentials, records, classifications, mappings, instructions, and other inputs supplied or made accessible by the Customer or its systems;
  2. "Product Output" means results, indicators, scores, mappings, alerts, findings, recommendations, transformed data, calculations, reports, logs, and other material produced or displayed by the Suite;
  3. "Human Review" means documented review by a competent and authorized person who can inspect relevant Source Data, understand disclosed limitations, seek additional evidence, disregard or override Product Output, and accept responsibility for the resulting action;
  4. "Material or Adverse Decision" means a decision materially affecting a person or organization, including education, employment, payment, credit, benefits, discipline, investigation, reporting, contractual rights, or another significant opportunity or burden; and
  5. the Customer is the controller and operator of its self-hosted environment and remains responsible for lawful authority, notices, permissions, data quality, configuration, roles, segregation of duties, retention, exports, backups, incident response, regulatory assessment, and decisions made from Product Output.

Connector is included integration fabric, not a Standalone Product, system of record, backup, archival service, or guarantee of semantic correctness or downstream processing. For every Suite, the Customer must have lawful authority to access each source and destination; comply with third-party terms; use dedicated least-privilege credentials and read-only access where feasible; validate extraction scope, identifiers, mappings, units, currencies, time zones, transformations, deduplication, ordering, reference data, and recipients; reconcile material counts and totals; protect credentials and exports; control event subscriptions, replay, retention, correction, and deletion of downstream copies; and revalidate integrations after source, schema, permission, or Product changes. Successful transfer proves only the recorded technical operation.

No Suite Schedule makes the Company the Customer's educator, school operator, employer, accountant, tax adviser, auditor, lawyer, compliance officer, data controller, fiduciary, system of record, or decision maker. Use of AI-assisted development tools by the Company does not transmit Customer business data to a third-party AI service unless an expressly documented Product feature does so and does not reduce the Customer's validation, Human Review, monitoring, or legal obligations.

Schedule A — Education Suite

A.1 Intended purpose and institutional responsibility

Education Suite supports admissions, academic delivery, school administration, learner and parent services, receivables and ledger operations and, according to plan, library, procurement, workforce, payroll, digital learning, payables, budgeting, and treasury workflows. It does not confer accreditation, authorize the Customer to operate an educational institution, determine the curriculum required by law, guarantee learning outcomes, attendance, progression, safeguarding, funding, payment, or regulatory compliance, or replace qualified educational, safeguarding, legal, accounting, or employment judgment.

The Customer remains solely responsible for institutional authorization; admissions criteria; curriculum and assessment policy; academic records; grading, progression, discipline, accommodations, safeguarding, mandatory reporting, and communications; the identity and authority of learners, parents, guardians, employees, contractors, and applicants; and every Material or Adverse Decision. Product Output must not be the sole or determinative basis for admission, exclusion, grading, discipline, special-support placement, employment, compensation, or another Material or Adverse Decision.

A.2 Learners, minors, privacy, and records

The Customer must determine and document the lawful basis for processing learner, child, parent, guardian, applicant, workforce, library, attendance, assessment, financial, and support data; provide required notices and obtain required consents or authorizations; verify guardian and representative authority; restrict access by role and need; apply age-appropriate and safeguarding controls; honor applicable access, correction, objection, export, retention, and deletion rights; and prevent disclosure between unrelated households, learners, classes, or companies.

Education Suite is not the Customer's exclusive archive. The Customer must maintain authoritative academic, attendance, assessment, safeguarding, employment, payroll, accounting, and statutory records for the periods and formats required by law, reconcile imports and migrations, and preserve a reproducible history of material changes, approvals, overrides, and communications.

A.3 Plan-specific safeguards

For Basic, the Customer must validate admission-to-receivable, learner charge, cash, journal, migration, academic calendar, enrollment, class, attendance, assessment, and guardian workflows before production use. For Pro, the Customer must additionally control library patron privacy, fines, procurement authority, supplier records, employment status, payroll inputs, transport access, and incompatible workforce duties. For Max, the Customer must additionally validate learning content and accessibility, assessment configuration, digital-learning completion, budget authority, commitments, payables, payment approvals, and treasury release controls.

No migration count, successful import, generated balance, completion marker, attendance state, grade, recommendation, or workflow approval proves that the underlying record is complete, lawful, pedagogically appropriate, or correct. The Customer must test representative and edge-case data, reconcile material populations and totals, monitor errors and access, and suspend affected use when integrity, privacy, or safety is in doubt.

Schedule B — Financial Suite

B.1 No accounting, tax, banking, or assurance service

Financial Suite supports ledgers, payables, receivables, tax evidence, treasury, bank reconciliation and, according to plan, fixed assets and budgeting. It does not provide accounting, tax, legal, investment, banking, audit, or assurance services; determine the accounting framework or tax treatment applicable to the Customer; guarantee that books close, statements are fairly presented, returns are correct, payments settle, assets exist, controls are effective, or records satisfy a regulator, auditor, lender, or investor; or replace appropriately qualified professionals.

The Customer remains solely responsible for its chart of accounts, opening balances, policies, periods, currencies, exchange rates, dimensions, counterparties, tax codes, source documents, recognition, classification, estimates, accruals, allocations, consolidations, eliminations, close, financial statements, filings, books and records, approvals, payment instructions, and compliance with accounting, tax, banking, corporate, employment, and record-retention requirements.

B.2 Completeness, reconciliation, and authoritative records

The Customer must identify complete relevant populations, reconcile subledgers and imported data to authoritative sources, investigate duplicates and gaps, validate journal balance and posting dates, preserve source documents and approval evidence, control period open and close, and maintain an independent backup and recovery path. A successful migration, balanced journal, zero, empty report, absent record, generated reconciliation, calculation, tax result, budget variance, or completed workflow does not establish completeness, accuracy, authorization, recoverability, or compliance.

Before production use and after material change, the Customer must test known-answer, boundary, duplicate, incomplete, reversal, multi-currency, tax, period-close, failure, retry, and recovery scenarios; validate mappings, calculations, permissions, event subscriptions, exports, and interfaces; document acceptance criteria and limitations; and obtain appropriate finance approval.

B.3 Payments, tax, assets, and budgets

The Customer must apply segregation of duties and approval limits to vendor setup, invoice entry, journals, bank details, payment preparation, approval, release, refunds, write-offs, tax configuration, asset capitalization and disposal, and budget changes. Treasury or payment Product Output is an instruction or workflow state, not confirmation from a bank or beneficiary; the Customer must independently verify material payment details and settlement and promptly contain suspected fraud or credential compromise.

Tax calculations and evidence depend on Customer configuration and Source Data and are not tax advice or a filed return. Fixed-asset records do not establish legal title, existence, condition, impairment, valuation, or tax basis. Budgets, forecasts, commitments, and variances are management tools, not guarantees of availability, performance, solvency, or future results. Qualified Human Review remains required for material postings, filings, payments, estimates, asset actions, close decisions, and external reporting.

Schedule C — GRC Suite

C.1 Analytical status and required Human Review

GRC Suite supports enterprise risk, obligations, policies, controls, evidence, concerns, screening, cases, issues, remediation, audit analytics and internal-control assessment in every Product Plan. Product Output is an analytical indication, not a verified fact, proof of wrongdoing, legal or regulatory conclusion, official screening decision, compliance certification, risk guarantee, control attestation, audit opinion, assurance conclusion, or substitute for an investigation or professional judgment. It may be incomplete, stale, ambiguous, false-positive, or false-negative and does not change status when scored, summarized, exported, sent through the event bus, or attached to another record.

Before reliance, the Customer must establish a lawful purpose and processing basis; validate Source Data, populations, rules, thresholds, watchlists, mappings, roles, jurisdictions, workflows, and recipients; document intended use, foreseeable misuse, affected groups, impact, error tolerance, escalation, override, contest, and remediation; apply qualified Human Review before every Material or Adverse Decision; independently corroborate allegations, sanctions, legal, regulatory, audit, control, and enforcement conclusions with authoritative evidence and qualified professionals; and preserve the reviewer, evidence, reasoning, overrides, and final decision.

The Customer must not use Product Output as the sole or determinative basis for a Material or Adverse Decision; represent it as proof, certification, opinion, attestation, legal conclusion, verified allegation, or Company endorsement; use it for unlawful discrimination, social scoring, covert surveillance, prohibited protected-characteristic inference, manipulation, retaliation, or punishment; or deploy it in a prohibited or high-risk context without required assessment, oversight, registration, authorization, and affected-person process.

C.2 Risk, compliance, concerns, and case management

For every Product Plan, the Customer remains responsible for its risk methodology, appetite, taxonomy, ownership, ratings, obligations, policies, control mapping, screening scope, investigation protocol, issue severity, remediation, certification, and regulatory reporting. Concerns and speak-up records may be highly sensitive: the Customer must restrict identity and case access, protect confidentiality and lawful anonymity, prevent retaliation, manage conflicts, preserve evidence, provide required notices and response rights, and meet non-waivable reporting and investigation duties.

No score, match, flag, control status, policy acknowledgment, case state, issue, remediation state, or certification establishes that risk is acceptable, compliance has been achieved, a person committed misconduct, or a control operated effectively. The Customer must monitor drift, bias, false positives, false negatives, complaints, overrides, access, and incidents and suspend or constrain affected use where integrity, rights, confidentiality, or safety is in doubt.

C.3 Audit analytics — every Product Plan

Audit is included in Basic, Pro and Max. The Suite does not perform an audit, review, agreed-upon procedures engagement, attestation, certification, or other assurance engagement under ISA, GAAS, PCAOB, IIA, or another professional framework. The Company is not the Customer's auditor and assumes no auditor independence, skepticism, evidence, documentation, reporting, or professional duty. The Customer remains responsible for engagement acceptance, competence, planning, complete populations, scope, sampling, materiality, tolerable error, assertions, procedure design, sufficient appropriate evidence, findings, communications, reporting, and remediation.

A zero, empty result, inaccessible field, unsupported format, timeout, refusal, successful run, reconciliation, ratio, trend, journal-entry candidate, or recommendation does not establish completeness, absence of fraud or error, or a required conclusion. A finding requires competent review of relevant and contrary evidence, documented criteria and assertion, and an authorized conclusion. Before an allegation, external report, disciplinary action, control conclusion, or other Material or Adverse Decision, the Customer must independently corroborate the matter and provide any process and opportunity to respond required by law or policy.

C.4 Internal controls — every Product Plan

Internal-control management is included in Basic, Pro and Max. The Customer remains responsible for control objectives, design, ownership, frequency, evidence standards, tester competence and independence, sample selection, exceptions, deficiency classification, aggregation, remediation, management attestation, and external reporting. A configured control, uploaded evidence, completed test, automated signal, workflow approval, or management attestation does not by itself prove design adequacy or operating effectiveness.

The Customer must test representative, boundary, incomplete, duplicate, manipulated, known-answer, access, failure, and recovery scenarios before production reliance and after material change; protect evidence and exports; segregate incompatible duties; preserve reproducible records; and promptly contain and investigate material security, integrity, confidentiality, or decision-quality incidents.

Schedule D — Farm Suite

D.1 Intended purpose and operating responsibility

Farm Suite supports planning, execution, animal and crop care, inventory, quality, maintenance, traceability and operational evidence for the Activity Profiles expressly certified in the purchased release. An Activity Profile is a versioned operating configuration inside the Product, not a separate Product, plan or price. A profile described as planned, discovery or unavailable is not part of the supported commercial scope until a later signed Product release admits it.

The Suite does not provide agronomic, veterinary, food-safety, environmental, engineering, legal or regulatory advice; guarantee yield, health, welfare, quality, traceability, resource availability or commercial results; certify a farm, product, treatment, withdrawal, movement, permit, filing or report; or replace appropriately qualified professionals and authorized public bodies. The Customer remains responsible for facilities, animals, crops, people, equipment, inputs, labels, prescriptions, biosecurity, welfare, food safety, water and land rights, environmental limits, emergency response and every physical or regulated action.

D.2 Global baseline and country overlays

The global operating baseline records non-regulated work, evidence, correction, segregation-of-duties and traceability invariants. It does not assert that one country's permits, labels, withdrawal periods, reporting formats, movement rules, veterinary authority, pesticide rules, water limits, welfare standards or retention periods apply elsewhere. A regulated action must remain unavailable unless the Customer has installed and selected a signed Product overlay applicable to the operating country, activity, species/crop and period.

The Customer must determine applicable law and competent authority, obtain and maintain permits and professional authorizations, validate Product policy sets against authoritative sources, keep jurisdiction and operating location current, and suspend affected use when applicability, evidence or authority is uncertain. A completed Workflow, green status, generated certificate, absence of an alert or successful event delivery does not establish legal permission or regulatory compliance.

D.3 Human review, AI assistance and physical execution

AI Agent Profiles in Farm Suite are supporting assistants only. They may help summarize Product records or prepare suggestions when a separately signed model, knowledge and verifier pack is enabled, but they have no business authority and must not approve, prescribe, apply, release, submit, post, certify or execute an operation. The Customer must ensure competent Human Review of AI output and must not treat it as a diagnosis, prescription, agronomic direction, safety clearance, quality disposition or regulatory decision.

The Customer must verify identity, object scope, current conditions, source data, units, dates, evidence, equipment availability, medicine/input status, withdrawal and quarantine restrictions and required independent approvals before physical execution. The Customer must reconcile actual field, herd, flock, greenhouse, inventory, laboratory, maintenance and traceability outcomes back to the Suite, preserve corrections and exceptions, and operate independent backup, recovery, incident and business-continuity procedures.

D.4 Plans and capacity

Basic, Pro and Max contain the same certified roles, workflows, components and supported Activity Profiles. The plans differ only by the numeric production- period admissions stated at checkout. A quota does not change legal scope, professional responsibility, country applicability, safety controls or the required evidence and Human Review. Idempotent retry of an admitted operation does not consume a second admission; exceeding a quota does not authorize a side-channel process or removal of controls.

16. Contact

Silkway Tech LLC — 5830 E 2nd St, Ste 7000 #30294, Casper, WY 82609, USA. Questions: via the support page.