Right-Sized Public Tech

Standards, disclosures, and corrections

How Right-Sized Public Tech selects sources, separates guidance from sales, handles corrections, protects consent, and approaches accessibility.

Source standard

Primary sources first.

Factual guidance must trace to a current official source that has authority for the statement, such as a regulation, government standard, official audit, official program guide, or agency publication. A news story, vendor page, search result, or summary may help locate a source, but it does not support a published factual assertion here.

Every factual resource names the source and a last-verified date. If a source cannot be reached or its current status is unclear, we remove or qualify the assertion. An absence of evidence is not treated as proof.

Jurisdiction-specific thresholds, purchasing routes, legal duties, and program requirements are not generalized. Readers are told to verify them with the responsible local officials and current official materials.

Review and versioning

Show what was reviewed and what remains unverified.

JS Technology Solutions, Inc. owns editorial responsibility. A substantive guide receives a source review and a cross-functional review covering the operational, procurement or finance, and technology or security perspectives that apply. A page names an external practitioner reviewer only with that person’s permission. The absence of a named external reviewer means no external review is claimed.

The public practitioner review record shows the current status, review method, editable packet, reviewer perspectives, completed-review count, and attribution boundary. It currently states that external review is prepared but not started.

Each substantive guide carries a publication or verification date. Material changes to recommendations, sources, decision steps, disclosures, or risk boundaries require a new modified date and a plain-language revision note. Formatting fixes do not create a new substantive version.

We do not describe publication, review, or contribution as government approval, certification, affiliation, or endorsement.

Editorial policy

The useful answer comes before the product.

We begin with the public team’s problem, current process, existing systems, constraints, users, data, approvals, and decision. Software is one possible response, not the default recommendation.

Tools must remain usable without an email address. Guidance does not promise savings, compliance, legal authority, customer outcomes, certifications, affiliations, or endorsements that have not been verified. We do not help shape a solicitation on which JS Technology Solutions may bid. General resources stay public and available on equal terms.

Each substantive review checks the operational-owner, finance or procurement, and IT or security perspectives. K-12 guidance also considers student privacy, accessibility, continuity, and limited staff capacity.

Corrections policy

Correct the record, preserve the reason.

Send a correction to jserle@jstech-inc.com with the page, statement, and official source. Do not include confidential procurement, student, personnel, resident, vendor, security, or incident information.

We review the cited official source, correct material errors promptly, update the verification date, and note a material correction on the affected page or in the source record. Minor spelling and formatting fixes may be made without a public note.

Material correction log

No material corrections have been recorded as of August 26, 2026.

Contributions

Practitioner review should improve the resource, not decorate it.

Public employees, auditors, researchers, advocates, and other practitioners may suggest a source, identify an operational gap, or volunteer to review a draft. A contribution does not guarantee publication, attribution, or an ongoing role.

Contributors must disclose relevant employment, vendor, client, funding, and procurement interests. We ask permission before publishing a person’s name, organization, or comments. We do not publish confidential or procurement-sensitive material.

Practitioners may use the editable review packet to test the AI procurement guide and worked example. The packet is ungated and does not submit data.

To propose a contribution, email jserle@jstech-inc.com with the resource, intended audience, and the operational decision it would help. Do not attach protected records or nonpublic procurement material.

Commercial disclosure

Published by JS Technology Solutions, Inc.

JS Technology Solutions, Inc. is the publisher of Right-Sized Public Tech and is also a software vendor. It offers RouteLedger and is exploring bounded pilots for GrantDesk, PortfolioDesk, and PermitDesk.

RouteLedger has a working demonstration. GrantDesk, PortfolioDesk, and PermitDesk are proposed pilot offerings, not finished working products. A related JSTK option appears only after the neutral field kit, inside a visually separate disclosure that states when it fits and when it does not.

The AI procurement scoping guide does not present a related JSTK product.

No payment, sponsorship, affiliate arrangement, customer status, government affiliation, or endorsement influences the source selection.

Accessibility statement

Designed and tested toward WCAG 2.2 AA.

We target WCAG 2.2 Level AA in design, implementation, and testing. This statement is not a claim of certified or complete conformance.

The field guide supports keyboard use, visible focus, semantic headings and form labels, reduced motion, responsive layouts, live status messages, and printable worksheets. We test common browser flows, zoom, contrast, and mobile behavior, then correct issues we can reproduce.

Report an accessibility barrier to jserle@jstech-inc.com. Include the page, task, browser or assistive technology if known, and the format you need. Do not include protected or confidential information.

Source register

Current factual foundation.

All sources below were directly checked on August 26, 2026.

Artificial Intelligence Risk Management Framework

National Institute of Standards and Technology. AI RMF 1.0 with current NIST resource updates.

Voluntary risk management across Govern, Map, Measure, and Manage, including trustworthiness considerations throughout the AI life cycle.

AI Guide for Government

U.S. General Services Administration. Living public guide.

Problem selection, organizational readiness, integrated teams, buy-versus-build decisions, testing, data rights, sustainable capability, and lessons learned.

Digital Services Playbook

U.S. DOGE Service. Current public edition.

User needs, iterative delivery, accountable ownership, security and privacy, and decision-linked measurement.

Capital Programming Guide, Version 3.1

Office of Management and Budget. Supplement to OMB Circular A-11, 2025.

Disciplined portfolio planning, prioritization, life-cycle cost, risk, acquisition, and performance management.

The NIST Cybersecurity Framework 2.0

National Institute of Standards and Technology. February 26, 2024.

A non-prescriptive set of outcomes across Govern, Identify, Protect, Detect, Respond, and Recover.

Data Security: K-12 and Higher Education

U.S. Department of Education Student Privacy Policy Office. Current resource hub.

Safeguarding student records, data security, data flows, retention, destruction, and online-service considerations.