cc3976fb7f
- Split competitive-analysis-2026-05.org → TOC + 9 competitor files in ideas/competitors/. Dropped date from filename. All competitor UUIDs generated, TOC keeps original UUID for backlink continuity. - Deleted passepartout-economics.org archive (replaced by 27-node KB). - Inlined 5 'See also' blocks into natural prose (compliance-index, first-mover-window, revenue-table, orders-of-magnitude-time, native-org-knowledge-base). - Linked 7 orphan compliance pages back to compliance index + finished truncated sentences. - Linked all 14 Agora requirement docs from topic-relevant pages (identity→lisp-machine-security, infrastructure→compute-marketplace, social-space→growth-strategy, exchange→agora-contracts, etc.). - Linked ai-industry-impact from investment-thesis, sufficiency-flip, verification-appliance, effects-growth-flywheel (up from 1 to 10+ pages). - Fixed CREATED timestamps to use git commit dates instead of today. - Made all links absolute from root (no port inheritance). - Removed stale agora/docs/ duplicate content.
1.2 KiB
ISMAP (Government Security Framework — Japan)
is moderate — few non-Japanese vendors target APPI specifically, and the 2022 amendments added requirements that created compliance gaps.
ISMAP (Government Information System Security Management and Assessment Program)
Japan's government cloud security program — analogous to FedRAMP. Cloud services used by Japanese government agencies must be ISMAP-authorized. Managed by the Digital Agency and the Information-technology Promotion Agency (IPA).
Who must comply: Cloud service providers selling to Japanese national and local government agencies.
Why it matters: Like FedRAMP, ISMAP is a procurement gate. Authorization is time-consuming and expensive. A compute marketplace provider with ISMAP authorization has exclusive access to the Japanese government market. First-mover advantage is significant — as of 2025, fewer than 100 services are ISMAP-registered.