Skip to content

P1-002 — Competitor Benchmark Refresh And Concrete CTC Gap Matrix

  • Task ID: P1-002
  • Execution result: COMPLETE — USER REVIEW PENDING
  • Status authority: No future roadmap or Task owner is assigned by this file
  • Lane: Cloud
  • Parallel: possible
  • Dependencies stated by user: none
  • Activation: the user's instruction to run the P1-002 competitor benchmark
  • Future unlocks: NONE ASSERTED
  • Completed: 2026-07-30
  • Product value: competitor marketing, current CTC facts, approved targets, and open questions are separated before any product-planning decision
  • Output: ../BENCHMARK.md
  • Background input: ../requirements/CTC_PRODUCT_PLATFORM_AND_DOCUMENTATION_RESET.md

Outcome

Refresh the competitor benchmark using current official material, separate public vendor claims from verified CTC current facts and approved CTC targets, add missing direct/specialist competitors, and produce a concrete gap/timing matrix without inventing future roadmap ownership.

Why Now

The user explicitly activated P1-002. No additional dependency, follow-up Task, status owner, or unlock condition was provided by the user, so none is inferred.

Product Value

The result makes later product decisions safer:

  • productization gaps are separated from raw feature gaps;
  • structural requirements are distinguished from post-stability feature candidates;
  • competitor claims do not become implementation facts or promises;
  • current market consolidation is reflected;
  • exact future planning remains subject to separate user approval.

Context And Problem

The previous benchmark contained useful direction but had material weaknesses:

  1. competitor-advertised capability, CTC current fact, and CTC target direction were not consistently separated;
  2. Scrap Dragon and ScrapRight were combined despite different product/package signals;
  3. current market evidence omitted Scaleit and did not reflect the GreenSpark/ReMatter combination into ReSpark;
  4. the first P1-002 revision incorrectly treated a provisional planning table as approved future work and assigned unsupported future ownership and dependencies.

The fourth issue is corrected by this revision. The benchmark now records findings and generic planning areas only.

In Scope

  • AMCS Metal / Brady;
  • cieTrade;
  • Scrap Dragon;
  • ScrapRight;
  • ReSpark, including bounded GreenSpark and ReMatter product evidence;
  • Scaleit;
  • Kaleris YMS;
  • Odoo multi-company/module/deployment patterns;
  • current CTC facts from current architecture and process evidence;
  • approved CTC target direction;
  • concrete gaps, timing classification, planning areas, unknowns, and official sources.

Out Of Scope

  • creating future Task or Phase IDs;
  • assigning future status ownership, dependencies, or unlocks;
  • changing the roadmap;
  • activating product features;
  • changing Product North Star;
  • independent vendor security or financial diligence;
  • customer-reference or implementation-quality verification;
  • exact vendor pricing where it is not public;
  • legal validation of compliance claims;
  • modifying Runtime, DB, provider, service, production, or deployment.

Must Preserve

  • competitor features are benchmark inputs, not automatic requirements;
  • current facts and target claims remain distinct;
  • unknowns are not converted to implementation facts;
  • CTC remains a lightweight recycling/logistics Operations ERP, not a general ERP;
  • one codebase, no customer fork, and no new numeric CLIENT_ID business branch;
  • reliable core and evidence before AI action;
  • compliance, payment, portal/mobile, broad hardware, RTLS/gate, advanced profitability, multi-site, and predictive/agentic AI remain post-stability candidates;
  • React and PostgreSQL timing are not changed by this benchmark.

Inputs And Affected Surfaces

Inputs reviewed:

  • docs/requirements/CTC_PRODUCT_PLATFORM_AND_DOCUMENTATION_RESET.md as background context, not authority for unapproved future Task IDs;
  • docs/PRODUCT.md;
  • docs/product/PRODUCT_CHARTER.md;
  • .agents/rules/SYSTEM_DESIGN.md;
  • .agents/rules/ARCHITECTURE.md;
  • docs/processes/process-registry.yaml;
  • prior docs/BENCHMARK.md;
  • official public vendor pages listed in the benchmark source register.

Changed surfaces:

  • docs/BENCHMARK.md;
  • docs/tasks/P1-002.md.

No Runtime or operator-manual surface changes.

Detailed Execution

  1. Confirm the user-requested P1-002 scope without inferring future plan ownership.
  2. Read current CTC fact owners and approved target owners.
  3. Review the previous benchmark and identify unsupported or mixed claims.
  4. Re-check required vendors using current official product pages and documentation.
  5. Add current direct/specialist candidates and classify direct, adjacent, and architecture-reference products.
  6. Record the GreenSpark/ReMatter combination as ReSpark and avoid double-counting.
  7. Separate OFFICIAL-PUBLIC, CTC-CURRENT, CTC-TARGET, and UNKNOWN.
  8. Build a concrete capability-to-gap-to-decision-to-planning-area matrix.
  9. Separate structural inputs from conditional post-stability features.
  10. Remove unsupported future Task/Phase mappings, dependencies, unlocks, and status-owner claims.
  11. Validate Markdown structure and perform GitHub read-after-write.

Deliverables

  • refreshed docs/BENCHMARK.md;
  • this P1-002 execution record;
  • direct competitor landscape;
  • current-versus-target CTC baseline;
  • concrete gap/timing/planning-area matrix;
  • post-stability boundary;
  • official source register;
  • explicit statement that future roadmap mapping remains undecided.

Acceptance Criteria

  • [x] Every required vendor family is reviewed.
  • [x] At least one missing direct/specialist candidate is added.
  • [x] Current market consolidation is reflected.
  • [x] Vendor claims are treated as public claims, not verified implementation quality.
  • [x] CTC current facts and target claims are separated.
  • [x] Every major gap has a decision timing and generic planning area.
  • [x] Structural work and post-stability features are separated.
  • [x] Rejected patterns and unknowns are explicit.
  • [x] Official source URLs and observation date are recorded.
  • [x] No unapproved future Task/Phase ID, status owner, dependency, or unlock is asserted.
  • [x] No Runtime, DB, provider, service, deployment, or master promotion occurs.

Verification

Check Result Notes
Single H1 and required sections PASS Static Markdown inspection.
Markdown table column consistency PASS All pipe tables have consistent header/body widths.
Relative links in changed files PASS Targets are existing repository paths.
Source-register URL scheme PASS HTTPS-only.
Claim-class separation PASS Four evidence classes are defined and used.
Required competitor coverage PASS AMCS, cieTrade, Scrap Dragon, ScrapRight, ReSpark/ReMatter, Scaleit, Kaleris, and Odoo.
Future-ID scan PASS Only the user-requested P1-002 identifier remains; no future Task/Phase mapping is asserted.
node scripts/docs/check-all.mjs NOT_RUN Connector-only environment has no repository checkout; no false PASS is claimed.
Runtime/DB/browser/field verification NOT_APPLICABLE Documentation research only.
GitHub read-after-write REQUIRED Performed after publication; the exact resulting commit is reported.

Stop Conditions

Stop and do not claim completion if:

  • an official source cannot distinguish a material capability from inference;
  • current CTC evidence is only target documentation;
  • a competitor feature would silently become an approved requirement;
  • a provisional or historical planning surface would be treated as approved future work;
  • the remote qa branch moves and the change cannot be safely based on the latest head;
  • a write would require force update, master direct commit, deployment, or unrelated-file overwrite.

Runtime / DB / Provider / File / Deployment Impact

  • Repository files: docs/BENCHMARK.md, docs/tasks/P1-002.md
  • Runtime: none
  • DB: none
  • Provider/service: none
  • Production/deployment: none
  • master: unchanged

Rollback / Fail-Forward

Source rollback is a revert of the P1-002 documentation correction commit on qa.

No DB, provider, service, Runtime, production, or deployment rollback is required because the change is documentation-only.

Evidence And Handoff

Research observation date: 2026-07-30.

Key findings:

  • GreenSpark and ReMatter are treated as the current ReSpark competitor, with legacy pages used only as bounded evidence.
  • Scaleit is included as a scale/hardware/package specialist.
  • Scrap Dragon and ScrapRight are analyzed separately.
  • The immediate CTC gap is reusable productization: explicit tenant/profile/module/process/adapter/provenance/UI/onboarding/repeatability.
  • Advanced competitive features remain conditional.
  • Future roadmap ownership and sequence are intentionally not assigned here.

Engineering and operation states:

Dimension State
Engineering Complete YES — scoped document deliverables prepared and statically checked
Released NO — a documentation commit to qa is not a product release
User Accepted PENDING USER REVIEW
Stabilized NOT APPLICABLE
Value Verified PENDING LATER APPROVED USE

Progress Log

Date Event
2026-07-30 Confirmed P1-002 from the user's direct instruction.
2026-07-30 Reviewed current CTC architecture, target product/design, process maturity, and prior benchmark.
2026-07-30 Re-checked required competitors using current official public material.
2026-07-30 Added ReSpark consolidation and Scaleit specialist coverage.
2026-07-30 Rebuilt the benchmark, gap/timing matrix, source register, and generic planning handoff.
2026-07-30 Removed unsupported future Task/Phase ownership, dependency, unlock, and status assumptions after user correction.
---

Source: docs/research/platform-foundation/2026-07-30/raw/competitor-benchmark-and-product-gap.md — ctc repository · This page is an English translation of the source document. Identifiers, file paths and code symbols are unchanged. A user instruction quoted inside the text is kept in its original language.