Contents Warnings Must Follow the Book, Not a Fixed Hierarchy

Reviewed by Dmytro Nasyrov on October 22, 2026.

Our first contents-numbering rule assumed one fixed order of parts, sections and chapters. A valid book did not follow that order. The final review replaced the universal hierarchy with ranking derived from the first appearance of each recognized label kind within that book.

The frontend's responsibility was advisory: warn a curator about plausible gaps without turning a numbering heuristic into permission to save or approve a source.

Recognize labels before ranking them

Frontend and backend shared byte-identical vocabulary files and a common 17-row example list. The recognizer supported the agreed word-first labels and number forms. A dotted value such as Section 1.1 was outside its label recognition rule. Sharing the examples mattered as much as sharing the vocabulary. Two implementations can read the same words yet disagree about which heading is recognized or how an unlabeled row participates. The example list made those interpretation boundaries reviewable on both sides.

Let the current contents establish the kind order

In the amended rule, recognized kinds took their rank from first appearance in the current book. It retained an unrecognized higher-level heading above the known kinds and preserved the intended depth of unlabeled entries. It did not force every source into a fixed part-over-section-over-chapter model.

This correction came from a concrete counterexample to the first design. The amended rule describes the implementation; the earlier hierarchy remains superseded design history.

Bound the noise and provide a destination

A warning focused the affected row. The curator could inspect its surrounding entries rather than search the entire document after reading a generic notice. The interface also connected the finding to the relevant field through accessible descriptions and a live region.

Large gaps were ignored and the visible list was capped. Those limits did not prove that a long numbering jump was correct. They stopped the heuristic from overwhelming the editor with low-value output.

Warnings never blocked Save or Approve. The person reviewing the actual source retained authority over a plausible exception. This was not an automated missing-chapter recovery system, and the UI did not expose restoration candidates.

Counterexamples that reject a universal hierarchy

A chapter at the top level with numbered sections below it produced no warning in the amended tests. In another case, the first chapter was followed by a section incorrectly placed at the same level; the warning expected that section at level two. First appearance established the relative kinds, while the entered depths supplied the position of the top kind.

A different fixture placed an unrecognized Unit I heading above two recognized chapters. The top recognized kind remained at its existing lower depth. Promoting every chapter to level one would have destroyed a valid outer grouping. Unlabeled entries had another rule: when nested below the preceding recognized entry, they kept that relative depth, capped at the supported maximum. The frontend did not issue level warnings for those unrecognized labels.

Reduced cases from the saved warning tests use synthetic outline entries and expected findings:

Chapter 1 -> Section 1 -> Section 2 -> Chapter 2
// Valid when sections sit below chapters.
Chapter 1 -> Chapter 22
// A gap of 20 missing numbers is reported.
Chapter 1 -> Chapter 23
// A wider gap is ignored by the bounded heuristic.
Section 1.1 Scope
// Dotted number: no recognized label under this rule.

The boundary at 20 is intentionally visible in the tests. A test for only a small missing chapter would not establish which side of the bound is inclusive. Nor should the wider-gap result be described as a clean bill of health: it means the heuristic abstained because that interpretation had become implausible.

A false series could come from ordinary words

Vitamin C followed by Vitamin D was a recorded example of why number recognition needed a bound. Roman numeral interpretation can turn those letters into 100 and 500. The gap guard prevents that pair from producing an enormous missing-series notice. It does not establish that every title beginning with a number-like word is recognized correctly.

The warning's destination was also testable. A gap between earlier and later chapters attached to the entry after the gap, with the neighboring entry retained as context. The curator could focus the row that makes the absence apparent. Requiring an explicit destination turned a plausible warning into an inspectable editing action while leaving Save and Approve available.

The shared examples supported the correction

The implementation checked vocabulary equality and the common example list. A browser scenario removed a middle chapter, observed a gap and added it back to clear the warning. That sequence verified that the advisory UI followed an editing transition, rather than merely rendering a fixed warning fixture. The source still records limitations. Titles beginning with a function word can produce a series-like match, and the live region was not debounced. We do not describe the merged warning feature as a complete document validator.

Evidence scope

The merge reports package, build and browser checks against the local development cluster. Backend build-time correction is a separate contribution. Stas's frontend case is the warning policy, shared interpretation and curator interaction.

A curator can inspect the row after a gap and accept a valid exception with Save or Approve. The heuristic supplies a warning, while that decision stays with the person reviewing the source.

FAQ

Last updated: October 22, 2026

Quick answers to common questions about custom software development, pricing, process and technology.

Expand all Collapse all

Search FAQs

Type to filter questions and answers. Use Topic to narrow the list.

Showing all 14

• How long have you been in business?

  Copy link Copies a direct link to this answer to your clipboard.

  Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).

• What services do you provide?

  Copy link Copies a direct link to this answer to your clipboard.

  Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).

• Where is Pharos Production located?

  Copy link Copies a direct link to this answer to your clipboard.

  Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.

• How big is your team?

  Copy link Copies a direct link to this answer to your clipboard.

  Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.

• What types of customers do you serve?

  Copy link Copies a direct link to this answer to your clipboard.

  We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.

• How is a custom software development company different from an agency?

  Copy link Copies a direct link to this answer to your clipboard.

  A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.

  Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.

• How much does custom software development cost?

  Copy link Copies a direct link to this answer to your clipboard.

  Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).

• How long does it take to develop a custom software application?

  Copy link Copies a direct link to this answer to your clipboard.

  Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.

• What industries does Pharos Production serve?

  Copy link Copies a direct link to this answer to your clipboard.

  Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.

• Why hire a software development company instead of building in-house?

  Copy link Copies a direct link to this answer to your clipboard.

  Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.

  Factor	In-house team	Software development company
  Time to assemble	3-6 months (recruiting + onboarding)	1-2 weeks
  Upfront cost	High (salaries, benefits, equipment)	Lower (project-based pricing)
  Specialized expertise	Limited to who you can hire locally	Access to 90+ engineers across blockchain, AI, FinTech
  Scalability	Slow (each new hire takes months)	Fast (scale up or down per sprint)
  Long-term commitment	Full-time employment contracts	Flexible engagement models
  Risk	High if key engineers leave	Company ensures continuity and knowledge transfer

  For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.

• What projects does Pharos Production not take on?

  Copy link Copies a direct link to this answer to your clipboard.

  Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.

• Why does Pharos Production use agile methodology?

  Copy link Copies a direct link to this answer to your clipboard.

  We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.

  This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.

• When should you NOT hire a custom software development company?

  Copy link Copies a direct link to this answer to your clipboard.

  Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.

  In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.

• What kind of projects has Pharos Production delivered?

  Copy link Copies a direct link to this answer to your clipboard.

  Here are three anonymized examples from our recent delivery history:

  FinTech startup - payment platform (MVP)
  Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.

  Healthcare provider - patient portal (Full product)
  Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.

  Crypto exchange - trading engine (Complex)
  Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.

  See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.

Stas Rysin is the Lead Frontend Developer at Pharos Production. His work covers the design system, reader interfaces and administration workflows of a professional learning platform for aesthetic medicine.