Displaying Only the Evidence Our Answer Contract Provides

Reviewed by Victor Sineglazov and Dmytro Nasyrov on October 22, 2026.

The first Ask payload contained Markdown and citations. The design also described richer evidence states, retrieval steps and withheld claims. Those additions were not part of the agreed response contract. Our frontend had to show the available evidence without reconstructing missing facts from persuasive answer text. A later implementation replaced the old Sources list with an Evidence panel. That was a real expansion, but it still did not deliver every capability in the earlier proposal. The proposal and the later panel had different capability boundaries.

Missing fields were a product boundary

In the early slice, we omitted evidence tiers, retrieval-step displays and a closest-passage action. A paragraph that sounds confident does not supply a structured confidence value. A citation list does not identify every claim it supports. Inferring those properties in the renderer would have introduced a second, undocumented evaluator. Refusals had a timing constraint as well. In that contract, the grounded flag became available at the terminal event. While streaming, a response still appeared as an answer. A completed refusal then used a neutral honesty block. The frontend could not truthfully display the final classification before receiving it.

The panel needed an answer-specific target

When richer citation data became available, a marker opened its own answer and citation. The separate evidence rail opened the last finished answer. These were different entry points, so they needed explicit target selection rather than one global current-citation variable that could drift as the thread changed.

At 1280 pixels and above, the recorded panel occupied 460 pixels beside the thread. Below that boundary it became a bottom sheet. We did not squeeze the answer into a desktop side-panel composition at 1024 pixels simply because both surfaces could technically be rendered.

A context request could fail without changing provenance

Full figure descriptions and transcript context came through a cited-document request. The implementation used a two-second deadline and fell back to the snippet when that request failed. Two seconds was a configured waiting limit, not a measured response-time percentile. The failure did not remove the machine-origin label. A shorter fallback must not become apparently more authoritative because the supporting context failed to load. The interface retained the distinction between a supplied excerpt and the larger context it had attempted to retrieve.

This also bounded the panel's name. Calling it Evidence did not establish clinical verification. Full licensed passage text, claim-level support, additional source tiers and in-application book search remained outside that implementation.

Inspecting the panel as a state machine

The provider tests made the target explicit as an answer identifier plus a citation index. A wide-screen fixture clicked Marker 2 and expected the panel to be open, the sheet closed and the target to be the first test answer's second citation. Choosing Card 3 changed only the citation index while keeping the panel open. That is a stronger assertion than checking whether an Evidence heading appears somewhere on the page.

expect(state()).toEqual({
  panel: true,
  sheet: false,
  target: { answerId: 'a-1', index: 2 },
  wide: true,
})

In this saved synthetic fixture, the identifiers are test values. They describe a state contract rather than a real reader conversation. Keeping both target fields prevents a subtle cross-answer failure: index two is meaningful only inside the answer that supplied it. A global selected index could continue to point at a valid-looking number while the panel displays another answer's source.

Closing also had observable behavior. With the opener still mounted, focus returned to that marker. A separate test removed the marker before closing, representing an answer replaced while Evidence was open. Focus then moved to the surviving rail. Preserving the old element reference without checking its lifetime would leave the close transition with nowhere useful to return.

Navigation preserved one surface and retired another

On wide screens, the provider fixture opened Evidence, changed the conversation pathname and expected the panel to remain open. Its narrow counterpart expected the sheet to close on navigation. Those policies serve different compositions: the desktop panel is a persistent part of the thread layout, while a phone overlay should not cover the newly selected conversation with stale context. Panel state lived in the client layout rather than browser storage. A panel remaining open across a route change did not promise that a reload would restore it. This lifetime choice belongs in the contract because otherwise the same word persistent could mean route continuity, reload continuity or cross-device synchronization.

None of these fixtures validates a medical claim. They establish which answer the person is inspecting and where the interface returns control afterward. Claim support still requires the separate evaluation that the early response contract did not supply.

What each merge record establishes

The early Ask merge reported its Markdown and refusal behavior in the prototype environment. The later panel merge supplied another implementation receipt and its own integration limits. We do not combine those records into a claim that every proposal capability was delivered or every browser check used real services.

Whether a cited passage supports a generated medical statement requires separate evaluation. The panel can make that evaluation easier to inspect while still being incapable of proving it by itself.

Each visible action must point to data the contract supplies. If a field is absent, we can hide the action, show an explicit limitation or change the service contract with the owning team. A missing claim-level support map stays missing even when the panel successfully opens a citation.

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.