AENET ecosystems PUBLIC GATEWAY
Sell on AENET · Early Access
GATEWAY READY
ENไทย中文
KAP-GRID / Y C01

DEVELOPMENT / KAPX IDE

KAPX-IDE · Product vision and direction

Explore an AI engineering environment designed around project coordinates, human control and development evidence, with current readiness and next milestones.

KAPX IDEDevelopment environment ExplorerLocal workspace
KAPX IDE → WORKSPACE → SERVICES → VERSIONSC01 · K.PUBLIC.DEVELOPMENT
Register service interest Getting started

Explorer runs in KAPX IDE on your computer. An online IDE service is not yet available from this page.

KAPX IDE / 0.4.6 /

Latest source report 0.4.6 · Explorer to reviewed work

VERSION and CHANGELOG checked on 2026-10-15; the observed IDE badge also showed 0.4.6. This is not end-to-end verification or a public installer release.

Select file → review draft → confirm

Explorer binds context to a file and scope before confirmed dispatch to existing ID01/ID02 terminals. Assignment controls stay above the scrolling tree.

Separate work rooms and status

Work stays separate from ordinary Chat and Human terminals, with per-ID recorded / running / replied / failed history. Stale files, timeouts and incomplete output remain explicit.

Model labels do not grant write authority

Candidate work does not automatically authorize canonical source changes. Requested model/effort labels are not provider attestations. Human acceptance is separate.

Earlier changes 0.4.1–0.4.5
  • 0.4.5 — ID02 status checks inside the IDE do not start new authorization; the Human verifies provider identity separately.
  • 0.4.4 — Isolated ID02 profile; Selection → Chat prepares context before Send.
  • 0.4.3 — Separate ID01 preserves the existing session and records per-ID provenance.
  • 0.4.2 — Chat reuses Tests/Debug results without analysis reruns; failed/cancelled builds do not launch debugging.
  • 0.4.1 — Scoped Search and Git diff context checks freshness before Add/Send.

Changelog summary only: no model, Tests or Debug executed for this report. Mockups use synthetic data and are not screenshots.

KAPX / DATA STRUCTURE

Page data structure

All content follows one data chain from product records to service status, comparison and evidence, so each surface has a clear source and next check.

Reviewed

  1. 01

    Product core

    Tools, roles, workflow, continuity and trade-offs come from the same Engineering.Products records used by Technology (8 current records).

  2. 02

    Service state

    Version, installer, connector and end-to-end readiness remain explicitly PLANNED or NOT_VERIFIED according to public evidence.

  3. 03

    Comparison table

    Read all 8 tools by row and 16 dimensions by column from one read-model; it is not a ranking or superiority score.

  4. 04

    Evidence and review

    Evidence status and review date stay separate from product claims, distinguishing source-observed parts from runtime checks still pending.

KAPX / TECHNOLOGY & ARCHITECTURE

Technology & Architecture →

Explore the program's architecture, technology and inspectable evidence. Each topic links to its section on the same Technology page.

Source and documentation evidence is not end-to-end verification or a service release. Each section identifies its evidence status.

KAPX-IDE · INTERNAL DEVELOPMENT

Engineering Beyond the Editor

Coordinate-Driven AI Engineering Environment

An engineering workspace designed to connect project understanding, AI-assisted changes, human review and development continuity.

Designed for Continuity. Built for Verifiable Engineering.

Keep context when work changes hands

Addresses repeated project explanation, disconnected tool results and unclear next steps when people or AI sessions change.

AENET contributors and developers evaluating projects maintained across multiple sessions; public onboarding remains planned.

Four design principles

01 / COORDINATES

Coordinates connect structure and ownership

Beyond a file tree, KGRID / DGRID / XGRID / FGRID describe components, ownership, relationships and work boundaries. Registry structures exist in source; complete runtime integration is not yet verified.

02 / HUMAN CONTROL

People define intent and authority

People define goals, scope and risk. AI assists through authorized tools; a model response or plan does not itself grant permission to change a system.

03 / CONTINUITY

Carry evidence into the next task

Connect source identity, context, verification and next actions so handoffs have a reference point. Structures and test definitions were inspected in source; end-to-end runtime behavior was not tested in this review.

04 / ECOSYSTEM

Start with AENET products

The initial goal is using KAPX to develop AENET Trading and related systems, reuse verification structures and measure repeated work before making performance claims.

From intent to evidence and the next task

Design workflow: define a goal → review project context → develop with configured tools → review changes and tests → record progress for the next session.

  1. Human intent
  2. KAPX workspace
  3. Models & tools
  4. Source & test checks
  5. Evidence & continuity
  6. Next development task

Understand each tool’s focus

Eight tools covering IDEs, local and cloud agents, context and human controls. This overview shares the Technology page's data and compares it with KAPX's currently evidenced components, not performance rankings or claims that other tools lack these capabilities. Vendor documentation reviewed on

Open the current comparison: KAPX plus up to two peers, or the complete 8-tool × 16-dimension matrix with sources →

Read the 8-tool comparison
Tool / documentationDocumented focus
KAPX IDE ↗

CANDIDATE

Product details →

Primary purpose
An engineering workspace designed to connect project understanding, AI-assisted changes, human review and development continuity.

Main workflow
Design workflow: define a goal → review project context → develop with configured tools → review changes and tests → record progress for the next session.

Continuity approach
Designed to retain goals, relevant context, reviewed progress and next steps across sessions. Installed end-to-end continuity is NOT_VERIFIED.

Trade-offs / checks
Public installer and connector remain PLANNED. Platform support, provider compatibility and workflow reliability need release-specific verification. External dependencies are still required.

Evidence / runtime status
The linked snapshot establishes source version only. The 2026-10-14 review records local interface observation and source-level design evidence. Installed end-to-end operation is NOT_VERIFIED; measurements are pending.

VS Code / GitHub Copilot ↗

NOT_VERIFIED

Product details →

Primary purpose
Develop and review alongside an editor

Main workflow
Develop and review in the editor

Continuity approach
Sessions and handoffs

Trade-offs / checks
Workspace isolation is not a security boundary; review permissions and changes.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

Cursor ↗

NOT_VERIFIED

Product details →

Primary purpose
Agent-assisted changes with action controls

Main workflow
Code changes with agent tools

Continuity approach
Workspace file access

Trade-offs / checks
File edits can save immediately; approvals are not a complete security guarantee.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

Windsurf / Devin Desktop ↗

NOT_VERIFIED

Product details →

Primary purpose
Coordinate local and delegated agent work

Main workflow
Work locally and delegate

Continuity approach
Agent Command Center / Spaces

Trade-offs / checks
Plan-specific limits and whole-workflow measurements: NOT_VERIFIED in this review.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

Devin Cloud ↗

NOT_VERIFIED

Product details →

Primary purpose
Delegate engineering work to a cloud session

Main workflow
Continue delegated work remotely

Continuity approach
Server-side sessions and queued messages

Trade-offs / checks
Cloud availability depends on rollout and plan access; usage consumes the plan quota.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

Continue ↗

NOT_VERIFIED

Product details →

Primary purpose
Customize models, rules and tools for development

Main workflow
Customize existing development workflow

Continuity approach
Rules, prompts and task model roles

Trade-offs / checks
Provider and tool configuration is part of the workflow; comparative cost NOT_VERIFIED.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

OpenHands ↗

NOT_VERIFIED

Product details →

Primary purpose
Compose agents and operate execution backends

Main workflow
Compose and operate agents

Continuity approach
Conversations and automations

Trade-offs / checks
Managed and self-hosted backends have different operational ownership; check each component license.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

Replit ↗

NOT_VERIFIED

Product details →

Primary purpose
Turn descriptions into projects and applications

Main workflow
Idea to tested application

Continuity approach
Project context and checkpoints

Trade-offs / checks
Mode and plan determine usage allowances; exact workload cost NOT_VERIFIED.

Evidence / runtime status
Official documentation reviewed; installed runtime not tested here.

Seven KAPX capability areas now covered

Explore each component's role and evidence status using the same records as the product technology page.

Read all 7 components and evidence states
  • Coordinate Architecture
    CANDIDATE · E01

    XGRID, DGRID, KGRID and FGRID organize visual structure, screen layout, navigation and typography. The design gives developers a consistent way to locate and discuss a part of the interface across updates.

  • System Composition
    CANDIDATE · E02

    Designed to connect independently maintained components into a shared development workflow. Clear responsibilities help people review a change and understand where related work continues.

  • Language & Project Understanding
    CANDIDATE · E03

    Includes source-level work on Thai requests and project context, intended to clarify the user's goal before development. Language accuracy and installed workflows still need task-specific validation.

  • Memory & Continuity
    CANDIDATE · E04

    Designed to retain useful project context, reviewed progress and next steps when returning to a project. This supports continuity across sessions; installed end-to-end integration remains NOT_VERIFIED.

  • Planning & Review
    CANDIDATE · E05

    Design work connects observations to proposed plans and improvements for human review. Users can assess the intended outcome and supporting evidence before accepting work; autonomous learning is not established.

  • Workspace, Terminal & AI
    LIVE · E06

    The local interface review observed Explorer, terminal controls and an AI sidebar in the IDE. The intended workflow brings project navigation and development tools together. Execution depends on configured tools, model providers and permissions.

  • Integration & Responsibilities
    CANDIDATE · E07

    Designed to make work passed between components understandable and reviewable. KAPX coordinates the workflow while operating systems and external providers retain their own roles. Public connector availability remains PLANNED.

What is evidenced, and what comes next

Source inspected
The linked snapshot establishes source version only. The 2026-10-14 review records local interface observation and source-level design evidence. Installed end-to-end operation is NOT_VERIFIED; measurements are pending.
Planned / not yet verified
Public installer and connector remain PLANNED. Platform support, provider compatibility and workflow reliability need release-specific verification. External dependencies are still required.

Inspect evidence by LIVE, VERIFIED_COMPONENT, CANDIDATE and PLANNED status →

Next milestone: complete one real product task

Have the AENET team use KAPX to scope, edit, test and hand off a product task with reproducible evidence before expanding availability.

KAPX IDE illustration: Explorer on the left, central editor, output below and AI workspace on the right
Illustrative interface with a sample project · Open to enlarge · Actual layout may vary by version and settings
Explore the program →

Choose a service for your project

Services are in pilot and scope review. Register interest to begin discussing your project.

Explore all KAPX services →
D01 · L01DevelopmentDevelopment services and KAPX IDE workspace D02 · L02APIRead-only public data interface D03 · L03ContractsVersioned schemas and response contracts D04 · L04Early AccessPublic intake and launch readiness D05 · L05IntegrationFuture integration adapter surface D06 · L06Use CasesApplied system workflows D07 · L07TourGuided architecture path D08 · L08KAPXKAPX design and integration services
AENET Cloud website version history

Follow recorded snapshots, their predecessors and change reports. A recorded snapshot does not establish deployment.

Loading version history…

    Latest snapshot data · Full history (JSON)

    Website development archive
    A05/B03/C03/D02 GATEWAY

    Public Gateway v0

    Created the public-safe entrance: static site, sanitized snapshots, boundary contract and boundary tests.

    Path
    public-gateway-v0
    State
    COMPLETE
    Date
    2026-08-16 · v0
    A05/B03/C03/D03 SHELL

    Public Gateway v0.2 — Multi-page Surface

    Multi-page public surface with clean routes, shared shell, KAP public contracts and an anonymous traffic channel.

    Path
    public-gateway-v0-2-multipage
    State
    COMPLETE
    Date
    2026-08-16 · v0.2
    A05/B03/C03/D04 MOTION

    Public Gateway v0.3 — Motion Interface + Coordinate Layout

    Coordinate-driven layout, a central motion grammar with 14 presets, layered field background, responsive mapping and a reduced-motion fallback.

    Path
    public-gateway-v0-3-motion-coordinate
    State
    COMPLETE
    Date
    2026-08-16 · v0.3
    A05/B03/C03/D05 LOCALIZE

    Public Gateway v0.4 — Adaptive Spatial Interface + EN/TH/ZH

    Content-aware adaptive spatial grid, motion orchestration v2, animated public system map, and full English / Thai / Simplified Chinese UI.

    Path
    public-gateway-v0-4-adaptive-spatial-localization
    State
    COMPLETE
    Date
    2026-08-16 · v0.4
    A05/B03/C03/D07 QUALITY

    Public Gateway v0.8 — Design & Search Quality Intelligence

    A build-time quality engine (Go) that audits the generated site — AENET DESIGN QUALITY, SEARCH READINESS, CONTENT QUALITY, a recommendation engine and safe auto repair — while never claiming a Goo

    Path
    public-gateway-v0-8-quality-intelligence
    State
    COMPLETE
    Date
    2026-08-16 · v0.8
    Website roadmap

    LAUNCH ROADMAP

    The public gateway opens in phases. Status reflects this repository's verified state — the system is not fully open.

    1. 01Public GatewayDone
    2. 02Search KnowledgeDone
    3. 03Early Access IntakeLaunch Gate
    4. 04Domain ConnectNext
    5. 05Traffic ObservationNext
    6. 06Private PreviewLater
    7. 07Account SystemLater