… the renewal request is reviewed after the supporting documents are checked against the relevant policy clause …
policy_2026.hwp · page 18Sources
Public APIsDocumentsDevicesProcessing
Index & parseTransformRetry & traceSoftware
SearchService APIOperator app01 / Product spotlight
Built for work that stays close to the source
Findoc · local-first document search
Find the clause.
Keep the source close.
Findoc is a desktop product in development for work where contract terms and policy clauses are buried in Korean HWP, PDF, and Office documents. It extracts, indexes, and searches them locally, then keeps source review in the same workflow.
View Findoc detailsPlanned Claude API: an opt-in, cited answer over passages a user selects. It is not live.
contract renewal conditions ⌘ K
Hybrid retrieval · sample results
… the operating team confirms the proposed timeline before the agreement is extended …
briefing.pdf · page 6Other products
Current development snapshot · 08 Oct 2026
Findoc is the focus; other prototypes remain available to explore.
Findoc is in development. The remaining six product concepts span early implementation and planning.
Implemented prototypes5
Planning concepts2
Product portfolio status · 7 initiatives totalMobile product lab
Native apps for photos, places, and daily routines.
Four iOS prototypes cover poster composition, photo curation, travel timelines, and outdoor routines. Two prototype build captures are shown below.
Field Stamp
Turns a photo into a composed poster: select the subject, check image quality, arrange the composition, and export a PNG.
Rollette
Photo curation logic that turns a large camera roll into a considered sequence, rather than another storage view.
Orbit Diary · Re:Apply
A travel timeline and an outdoor routine tracker explore different forms of personal context, review, and return.
03 / Engineering
From source data to operating software
Build the path, then make it observable.
JinsongTech works where data enters, systems meet, and operators need a reliable next action.
Data pipelines
Public data, devices, APIs, webhooks, and databases connected with transformation, duplicate handling, retry, and operational visibility.
Service APIs
Business rules translated into service boundaries and integrations other teams can use without rebuilding the same manual steps.
Operating software
Focused tools for monitoring, exception handling, and handover when a spreadsheet and a message thread are no longer enough.
AI operating model
Specialist agents, accountable delivery
An agent team.
One accountable founder.
Findoc is planned as the first evaluation setting for Claude Code: document-to-search work units will be planned, implemented, independently verified, and approved by the founder. The same operating pattern is planned for reuse across other products and contracted work. Codex supports current development.
- Brief
- Architecture
- Parallel build
- QA & security
- Founder release
Product managerTask card · scope · acceptance criteria
A product brief becomes task cards with users, constraints, scope, and acceptance criteria. The founder reviews these before implementation starts.
CTOBacklog · technical risk · delivery slice
The backlog and repository context guide technical choices, dependencies, and delivery order. The output is a bounded implementation plan with risks and checks for the founder to review.
ArchitectureADR · data flow · API contract
Requirements and existing code inform component boundaries, data flows, and API contracts. Architecture decisions document trade-offs so implementation and review use the same assumptions.
FrontendAccessible UI · responsive capture
Approved flows and UI requirements guide screen implementation. Responsive captures, keyboard checks, and interaction review provide evidence for acceptance.
BackendAPI behavior · parsing · error paths
API contracts and sample inputs guide service logic, document parsing, and integrations. Code changes include checks for normal inputs, errors, and recovery paths.
QATest report · regression evidence
A separate verification pass receives the changed code and acceptance criteria. It runs relevant tests, records reproducible findings, and returns a verdict for fixes or founder review.
SecurityAccess review · dependency findings
Changed code and configuration are reviewed for access boundaries, dependency risks, and data exposure. Findings return to implementation before the founder approves a release.
Finance & accounting plannedEstimate draft · invoice draft · expense summary
Planned inputs are project scope, approved rates, and expense records. Agents would prepare estimate and invoice drafts or expense summaries; the founder would confirm amounts and records, with professional accounting review where needed.
Current practice: Codex supports active development. Claude Code is being evaluated for the planned Findoc workflow described above.
Engineering evidence
Local verification · 8 October 2026
Working code. Recorded results.
We keep development history and repeatable checks alongside the product. These results describe local prototypes and the specific samples tested.
- 01
Claude in Findoc’s development history
A 5 July 2026 Findoc commit credits Claude Opus as a co-author. It records panel-level error isolation, search logic extraction, and search-result normalization, with tests and review documented in the commit.
The founder also reports using Claude Code at an employer through a separate company account. JinsongTech currently uses Codex and is evaluating a Claude Code agent workflow.
- 02
Findoc · 12 tests passed
The existing Rust parser CLI produced non-empty output from eight fixtures: PDF, DOCX, HWPX, Markdown, TXT, HTML, JSON and EML. Two text fixtures also passed a targeted keyword check. Twelve selected parser and facade tests passed with no failures. These fixture outputs and tests do not verify end-to-end search across the full document workflow.
Explore Findoc ↗ - 03
Rollette · 18 photos to 10 selections
The macOS prototype used Apple Vision to analyze 18 sample photos, detect one near-duplicate group and select 10 images. The shared Swift core passed 36 tests with no failures.
Explore Rollette ↗
The 8 October verification runs were performed with Codex. They establish the tested local behavior, not customer adoption, revenue or App Store release. Claude attribution in the development history is separate from product API integration; no live Claude API feature is claimed. Test commands, timestamps and result hashes are retained privately.
05 / Work with us
Software development and solution consultation
Start with the system that is holding the work back.
We scope custom software projects and solution adoption for data integration, operational software, and service APIs.
- 01
Scope
Clarify users, systems, constraints, and an acceptance path before implementation begins.
- 02
Implement
Review working integrations, workflows, APIs, or screens in visible stages.
- 03
Hand over
Document the decisions and deliver an operating path that the next owner can follow.
06 / Relevant background
Founder experience before JinsongTech
Domain knowledge shaped in production environments.
These are the founder’s project contributions at previous employers, not JinsongTech customer work.
Connected city data
CityDataHub, NGSI-LD, JSON-LD, mapping, and digital-twin integration work.
Service platform design
Microservices connecting commerce, mobility, payment, and operational services.
Streaming ingestion
Flume and Kafka flows, context mapping, reprocessing, and duplicate prevention.
Unmanned parking
External notifications, asynchronous work, and webhook failure handling.
JinsongTech / Company
Software that earns its place in the operation.
JinsongTech began in Ulsan in June 2026. Founder SangYong Jeon leads product direction and delivery with experience in data integration and service operations.
The first planned Claude API feature is an opt-in, source-cited answer over passages a Findoc user selects; it is planned for evaluation and is not live.
Start with the problem, not a slide deck