Summary

  • A 2019 telecommunications authorization, a later concession record, two 2024 coverage entries, a public service interface and one IPv6-visible autonomous system show how Sergio Hernandez Cisneros became legible across Mexico's regulatory and network systems.
  • Sergio Hernandez Cisneros appears in public through a sequence of working documents. The first is a 2019 authorization for a telecommunications-service commercializer. A current regulatory entry later identifies him with an active concession record and internet and data-transmission services. A commercial-practices code defines the provider-consumer relationship. Two registrations from 2024 attach service coverage to named places in the municipality of Huanimaro. A public website presents a service interface. RIPEstat, finally, identifies his name with AS270218 and shows that autonomous system announcing an IPv6 prefix.

Sergio Hernandez Cisneros appears in public through a sequence of working documents. The first is a 2019 authorization for a telecommunications-service commercializer. A current regulatory entry later identifies him with an active concession record and internet and data-transmission services. A commercial-practices code defines the provider-consumer relationship. Two registrations from 2024 attach service coverage to named places in the municipality of Huanimaro. A public website presents a service interface. RIPEstat, finally, identifies his name with AS270218 and shows that autonomous system announcing an IPv6 prefix.

That sequence is more useful than a conventional origin story. It makes visible a set of decisions under different constraints: applying for a defined legal permission, operating within the limits of that permission, appearing later in the role of a concession holder, documenting how service is contracted, registering geographic coverage and maintaining an identity in the global routing system. None of those records explains private intentions. Together, however, they show how an activity acquires institutional form.

The distinction matters because the documents operate at different layers. The 2019 authorization concerns a commercializer using capacity obtained from concessioned public networks. The later concession materials describe a natural person authorized to install, operate and exploit a public telecommunications network. Coverage registrations concern places and dates. The website concerns the public presentation of services and account functions. Routing data concerns the visibility of an autonomous system. One layer cannot be used as proof for another.

This is therefore a profile of observable commitments rather than reputation. Hernandez is important to the record because his name is the point at which regulatory permission, consumer-facing documentation, registered coverage and routing identity meet. The organizational result is not a claim about scale or performance. It is a structure that can be inspected: a named responsible party, a service identity, a set of formal obligations, a dated geography and a network number visible through public routing data.

The first public decision was an authorization request

The earliest document in this record is the 2019 IFT commercializer authorization. It names Sergio Hernandez Cisneros as the recipient of authorization IFT/223/UCS/AUT-COM-341/2019. The document says that he submitted the request in his own right on September 26, 2019. It also records an IFT office decision dated October 17, 2019 to grant the authorization after the applicable administrative process.

The legal category is precise. The instrument authorized Hernandez to establish and operate or exploit a telecommunications-service commercializer without having the status of a concessionaire under that document. It defined a commercializer as a person providing telecommunications services to end users through capacity from one or more public telecommunications networks, while not itself occupying the concessionaire role. That definition fixes the initial organizational position more clearly than a broad description of an internet business could.

The request was a visible decision because it placed the proposed activity inside a rule-bound system. The document identifies the applicant, the requested legal form, the responsible regulator and the date on which the permission was granted. It does not describe what Hernandez thought about the process. It does show that the service activity was presented to the IFT through a formal request and accepted under a category with specified limits.

Those limits are part of the story, not background detail. The authorization did not grant exclusivity. It had a stated ten-year term from issuance, subject to the rules governing any extension. It required services acquired for commercialization to be entered in the public register before they were provided, along with the applicable tariffs under the relevant provisions. The authorized party also had to work through agreements with concessionaires whose public networks supplied the capacity.

This arrangement exposed both institutional and capital constraints. The instrument did not state a budget, equipment list or financing plan, so none can be reconstructed from it. What it did state was the resource model recognized by the authorization: service could be offered by obtaining network capacity rather than by treating the authorization itself as a network concession. The legal permission and the underlying network resources were separate entities.

The organizational outcome in 2019 was correspondingly bounded. Hernandez acquired a documented route for commercializing public telecommunications services, subject to registration, contractual and service obligations. That is meaningful because it moved the activity from an unrecorded possibility into an identifiable regulatory position. It is not evidence for every later stage. It is the first fixed point from which the later stages can be read.

A commercializer was a constrained position

The authorization's operating conditions explain why the word "commercializer" should not be treated as a decorative label. Services were to reach end users through capacity on public telecommunications networks operated by concessionaires. Agreements with those concessionaires had to supply the legal and operational link. If radio-frequency bands were involved, the authorized offering was limited by the coverage permitted under the relevant operators' concession titles.

This created dependency by design. Hernandez could hold the commercializer authorization, register services and present an offering, yet the permitted structure still relied on network capacity obtained from other authorized networks. The document did not erase the distinction between the party dealing with the end user and the party holding the underlying network concession. It made that distinction administratively visible.

The authorization also converted ordinary operating choices into recordable obligations. Services and tariffs had to be registered before provision. Agreements with concessionaires, and specified changes to those agreements, were to be submitted to the public register within the applicable period. The public-facing offer therefore sat downstream of filings, contracts and the legal capacities of other network operators. Time entered the system through those preconditions.

For a small telecommunications activity, these requirements matter because they organize sequence. Permission comes before the offer. A capacity agreement comes before service dependent on that capacity. Registration comes before public provision of the registered service. A tariff is not merely a number displayed to a prospective user; within the authorization framework, it belongs to a regulated chain. The document shows the chain even though it does not reveal the internal work required to maintain it.

The conditions also make clear why authorization cannot be read as an operating report. They state what the authorized party had to do and the boundaries within which the service had to be commercialized. They do not prove that every obligation was performed in every instance. A rule is evidence of the governing framework. Evidence about implementation would require a different record.

This distinction is central to a Sofia profile. Hernandez can be described through the decision to seek the authorization and through the role the IFT assigned to him. The constraints can be described because the instrument states them. But the article should not convert legal requirements into undocumented claims about execution. The first phase of the public record is strongest when it remains what it is: a defined, dependent and time-limited commercializer position.

The later concession record changes the frame

The IFT Public Registry of Concessions entry presents a later and materially different surface. It lists Sergio Hernandez Cisneros, reports the status as VIGENTE and associates the record with internet and data-transmission services. It also displays the service wording "SIW Telecomunicaciones / Soluciones Inalambricas Internet y Videovigilancia." That page should be read as the regulator's current concession record, not as a restatement of the 2019 commercializer instrument.

The difference in role is supported by the commercial-practices document as well. That first-party code describes Hernandez as a natural-person concession holder and frames the service around a single concession for commercial use. It says the provider is authorized to install, operate and exploit public telecommunications networks for internet access. The later record therefore places him in a network-concession frame that the 2019 authorization explicitly did not confer.

The available materials do not establish every intermediate administrative step, and they should not be turned into an undocumented account of how each one occurred. The defensible sequence is narrower: a commercializer authorization was granted in 2019; later public records identify Hernandez as a concession holder; and 2024 registrations modify coverage under that concession record.

That restraint does not weaken the analysis. The change in legal position is visible without inventing the missing administrative narrative. In 2019, the authorized model depended on capacity from concessioned networks. In the later code, the service is described through physical infrastructure attributed to Hernandez and a concession to operate public telecommunications networks. The documents show two distinct institutional arrangements across time.

The distinction also changes what can be organized under the named person. A commercializer authorization connects a person to the resale or commercialization of services under defined dependencies. A concession record connects the person to authority over a public network and to coverage modifications entered under that title. The later role can carry geography, infrastructure and service obligations in a different way.

What remains constant is personal identification in the formal record. Hernandez's name is not inferred from a promotional profile or a same-name account elsewhere. It appears in the IFT instruments and in the service code. That repeated, source-specific identification is enough to anchor the article while avoiding claims about titles or corporate structures that the documents do not establish.

Names have to remain attached to their records

The service identity appears with three spellings, and each belongs to a particular source. The IFT concession page uses "SIW Telecomunicaciones" together with the expanded wording "Soluciones Inalambricas Internet y Videovigilancia." The commercial-practices code defines "SIIV Telecomunicaciones" as the commercial name used by Sergio Hernandez Cisneros. The public site uses the SIIVV presentation in its domain and visible service surface.

These labels are clearly close, but closeness is not permission to rewrite the documents. Here, SIIVV serves as a practical display convention for the public website and the combined record. The regulator's page remains SIW, and the commercial-practices code remains SIIV. That approach keeps the reader oriented without claiming that every spelling has the same legal function.

Name discipline matters because identity is an operating layer of its own. A regulator indexes a concession under fields suited to public administration. A service code defines terms for a contractual relationship. A website presents a name that users can recognize. Variations may be mundane, but a careful profile should not silently normalize them and then use the normalized label to support conclusions that only one source makes.

The same discipline applies to Hernandez's role. The IFT records name a natural person. The website presents a service identity. The code connects the two by naming Hernandez as the provider and defining SIIV Telecomunicaciones as a commercial name. That is enough to describe a relationship among person, service and records. It does not require adding a corporate office or ownership structure absent from the package.

The commercial-practices code makes obligations visible

The SIIVV commercial-practices code is the document that most directly joins the named person to an everyday service relationship. Its stated objective is to describe internet-access and bidirectional data-transmission services provided by Sergio Hernandez Cisneros under an IFT concession, while setting out the rights and obligations of users. The code therefore operates between regulatory authority and the practical terms of receiving service.

Its definitions make the relationship explicit. Hernandez is named as the concession holder and as the party providing the service. SIIV Telecomunicaciones is defined as the commercial name. Internet access and bidirectional data transmission are defined as services offered under registered tariffs, conditions and speeds. The code describes bidirectional transmission as the transfer of information in real time through physical infrastructure between fixed user terminals using Internet Protocol.

That language is useful because it shows how a network becomes a repeatable offering. Technical infrastructure alone does not specify who contracts with whom, what service category is selected or which terms govern payment and activation. The code supplies those administrative interfaces. It refers to packages or modalities, a standardized agreement, applicable tariffs, documentation for contracting and procedures for changes, faults, cancellation and assistance.

The code should still be treated according to its provenance. It is a document published on the service site and written to state the provider's commercial practices. It is evidence of the framework the provider presents, not independent measurement of how every connection or interaction unfolded. Its detailed obligations reveal organizational design. They do not by themselves verify performance against those obligations.

The design is nevertheless consequential. A standardized relationship makes actions repeatable across more than one transaction. It assigns a provider, identifies a user, defines a service, points to registered terms and describes procedures when the relationship changes or the service is interrupted. Those are organizational results because they turn technical capacity into a service that can be requested, documented, billed, adjusted and ended through stated rules.

The code also reflects time constraints at a different scale from the concession. The 2019 authorization worked on a multi-year legal horizon. Coverage entries fix particular dates. A service code works through recurring operational moments: contracting, activation, payment, assistance, modification and cancellation. Hernandez becomes visible not through personal description but because the document assigns responsibility at each of those moments.

The website is an interface, not an outcome

The SIIVV public website adds a thinner but still important layer. It presents a Huanimaro-facing internet service surface with navigation for fiber and wireless offerings, along with payment and customer functions. Where the authorization and concession pages speak in the language of legal capacity, the website organizes the operation around tasks a person approaching the service might need to perform.

The presence of both fiber and wireless navigation indicates that the public presentation distinguishes delivery categories. It does not, without additional evidence, establish the architecture used for any particular connection. Nor do payment and customer links establish how often they are used. Their significance is procedural: the operation exposes paths for learning about services and managing an account through a recognizable public interface.

This is an organizational outcome in a modest sense. A public service interface requires categories, documents and recurring actions to be arranged for users rather than kept inside the operator's internal workflow. The commercial-practices code can be reached from the same service domain, linking the public presentation to a document that names the provider and defines the contractual structure.

The site also helps explain the display convention. SIIVV is the outward-facing form attached to the domain, while SIW and SIIV remain attached to the regulator and the commercial code respectively. The website does not erase those other labels. It supplies the name encountered at the consumer-facing layer.

Two 2024 entries make geography legible

The concession becomes geographically specific through two public registrations in 2024. The March 2024 IFT coverage entry records a modification to the concession title. Registration number 078875 was entered on March 19. It identifies Sergio Hernandez Cisneros, the services of internet and data transmission, and expanded coverage for La Lobera, also identified as El Rinon, in the municipality of Huanimaro, Guanajuato.

The same entry gives March 14, 2024 as the start date for service provision associated with that coverage. The distinction between start date and registration date matters. The document does not collapse them: one marks the stated beginning of service for the listed area, and the other marks entry in the Public Registry of Concessions. Administrative visibility followed through a dated registration.

Less than a month later, the April 2024 IFT coverage entry records another modification. Registration number 079714 was entered on April 16. It lists Huanimaro, La Cantera, Paso de Carretas and San Isidro de Ayala, all in the municipality of Huanimaro, and again identifies internet and data-transmission services under Hernandez's name.

That second document gives April 15, 2024 as the start date for the listed coverage. Read together, the two entries create a compact sequence: La Lobera in mid-March, followed by four named localities or areas in mid-April. The records do not provide a construction diary or explain the technical path into each place. They do show that coverage was formalized through two separate modifications with different dates and registration numbers.

The decision visible here is not simply "expansion" in the abstract. It is the attachment of specific geography to a concession record. Each entry converts place names into administrative commitments associated with a named holder and stated services. That makes the service area inspectable at a level more precise than a general claim to serve Huanimaro.

There is also an organizational implication in the cadence. Separate registrations mean that geography did not appear as one undated block. The public record was updated as additional coverage was entered. This requires coordination among the service plan, the concession conditions and the registry process, even though the documents do not expose staffing, equipment or expenditure behind that coordination.

Coverage is a dated administrative entity

Coverage documents are easy to overread because place names feel concrete. The March and April entries establish that the concession record was modified to include the listed locations for internet and data-transmission services. They do not state how many premises received a connection, how traffic was distributed, how the access network was built in each locality or what an individual user experienced.

The records are strongest as evidence of scope and timing. They identify the holder, the services, the named areas, the registration dates and the corresponding service-start dates. Those fields allow comparison across documents without requiring a speculative map. La Lobera is not a vague regional reference. La Cantera, Paso de Carretas and San Isidro de Ayala are not inferred from promotional language. They are written into IFT registrations.

This administrative meaning also limits the conclusions that can follow. A coverage commitment is not a census of active connections. A service-start date is not a continuous history of the service after that date. A modification to a title is not a report on financial return. The article can say that the authorized geography became broader and more specific in the register. It cannot convert that fact into an unsupported social or commercial result.

The restraint is analytically useful. It leaves room to see what the documents actually reveal about organization. Hernandez's operation had reached a point at which locations and dates could be attached to the concession in formal entries. The service identity was no longer visible only through an authorization or a website. It had a registered geographic surface that could be read place by place.

AS270218 adds another kind of visibility

The regulatory record explains who is authorized and where coverage is registered. It does not by itself show how the network appears in interdomain routing. That layer becomes visible through the RIPEstat autonomous-system overview for AS270218. In the July 22, 2026 observation, the endpoint returned the holder as "AS270218 - SERGIO HERNANDEZ CISNEROS" and marked the autonomous system as announced.

An autonomous system number is a routing identifier, not a general business credential. It gives a network a coordinate in the system through which independently administered networks describe reachability. The holder field connects AS270218 to the same personal name present in the IFT and service records. That correspondence is the reason the routing source belongs in this profile.

The connection across records should still be kept exact. The IFT materials establish regulatory roles and service coverage in Mexico. RIPEstat reports the holder and observed announcement state of an autonomous system. The routing endpoint does not restate the concession, and the concession page does not verify routing. The article brings them together because they identify Hernandez at complementary layers, not because one source validates every field in the other.

This is a concrete organizational result. A name, service and coverage record have been joined by a queryable network identifier. Yet the result remains bounded. The overview does not disclose the internal topology, equipment inventory, workforce or traffic carried by the network. It establishes an announced ASN and a holder name. Those are meaningful facts without needing to become a proxy for scale.

The IPv6 record sets a hard technical boundary

The RIPEstat routing-status record for AS270218 makes the technical claim narrower. In the July 22, 2026 observation, the autonomous system was visible with the IPv6 prefix 2806:401::/32. The record reported last_seen as 2026-07-22T00:00:00. It showed zero announced IPv4 space.

That combination has to govern the language used about the network. AS270218 can be described as IPv6-visible in the checked routing data. It cannot be presented as carrying an observed IPv4 announcement on the strength of this record. The announced=true field in the overview and the IPv6 prefix in routing status fit together, while the zero IPv4 figure prevents a broader dual-protocol description.

The timestamp is equally important. Routing data is observational and time-bound. The July 22 value establishes recency for that observation, not permanence. A route can be observed at one point and the surrounding routing system can later change. Preserving the timestamp keeps the claim auditable: this was the visible state returned at the stated time.

The prefix also should not be translated into claims the endpoint does not make. It does not describe the physical path to La Lobera or Paso de Carretas. It does not reveal whether a particular household used IPv6, how traffic moved within the access network or what upstream arrangements produced the observation. It identifies address space visible through AS270218 at the interdomain layer.

This boundary is not merely technical caution. It demonstrates how a person-centered profile can remain rigorous when the evidence changes form. Hernandez's name in an IFT document carries a legal meaning. His name in the ASN holder field carries a routing-registry meaning. The IPv6 prefix carries a reachability observation. Keeping those meanings separate allows the records to reinforce one another without being stretched.

The resulting description is precise: AS270218 was announced and visible through 2806:401::/32 in the checked RIPEstat data, with no IPv4 announced space reported. Precision matters more than making the network sound larger or more conventional. The visible protocol boundary is part of the identity of the record at that date.

Legal, commercial and routing time do not move together

The public outline spans nearly seven years, but it is not a continuous diary. September and October 2019 establish application and authorization. Later concession materials establish a different regulatory role without supplying every intermediate event in usable form. March and April 2024 establish specific coverage modifications. July 2026 supplies a fresh routing observation. Each source has its own clock.

Those clocks correspond to different institutional processes. An authorization follows submission and regulatory decision. A coverage modification follows the conditions and registration path of a concession. A commercial-practices code organizes recurring service relationships. A website can change as public functions are presented. Routing status is observed repeatedly by measurement systems. Expecting all of them to update in one synchronized narrative would misunderstand the record.

For Hernandez, the sequence is informative precisely because the clocks align only at certain points. His name recurs across them. Internet access and data transmission recur across the concession and coverage materials. The service identity recurs across the code and website, though with source-specific spelling. AS270218 adds a network identifier at the latest checked point. Continuity comes from those correspondences, not from a complete account of every month.

This has practical consequences for interpretation. The 2019 commercializer model should not be projected unchanged onto the 2024 concession modifications. The 2024 coverage entries should not be used to describe the exact routing state in 2026. The 2026 routing state should not be read backward as proof of a route in 2019. A disciplined chronology prevents later visibility from rewriting earlier legal facts.

Time is also a constraint on organization. Permissions have terms. Registrations carry dates. Service procedures recur. Routing observations expire as descriptions of the present. The public operation must therefore be maintained in more than one temporal system. The documents do not show who performed that maintenance, but they show the outputs: active regulatory status, dated coverage entries, a public service code and a recently visible IPv6 route.

The profile becomes more credible by admitting its gaps. There is no need to fill the years with imagined milestones. The visible points already show a transition from authorization through concession-linked coverage to routing presence. Gaps remain gaps, and the sequence remains useful.

Institutions form part of the operating surface

It is tempting to separate paperwork from network operation, treating the former as administrative overhead and the latter as the real story. The Hernandez record does not support that separation. The authorization defines what kind of service relationship was initially permitted. The concession page identifies the later holder and services. The commercial code defines the relationship with users. Coverage modifications define named areas. Routing records define technical visibility.

These documents do not carry packets, but they organize the conditions under which a public telecommunications service can be identified and used. A person needs to know the service identity. A regulator needs a named holder and registered scope. A standardized agreement needs defined parties and procedures. Other networks need a routing identifier. The operation becomes legible because these interfaces exist together.

Capital is visible only indirectly in this structure. The 2019 authorization recognized a model based on capacity acquired from concessioned public networks. The later service code refers to physical infrastructure attributed to Hernandez, and the coverage records attach the concession to additional places. The cited documents do not state spending or asset values. What can be observed is a change in the legal and infrastructural vocabulary surrounding the same named person.

Institutional constraint is more explicit. The commercializer authorization imposed conditions and dependencies. The concession record carries its own scope and modifications. The code places service within tariffs, agreements and procedures. Routing visibility is constrained by what is actually announced and observed, in this case one IPv6 prefix and no reported IPv4 space. At every layer, the usable claim is shaped by a system Hernandez does not define alone.

That is why the organizational outcome should be described as legibility rather than triumph. By 2024, the public could inspect named coverage modifications. Through the service domain, it could inspect a commercial-practices code and reach payment or customer functions. Through RIPEstat in 2026, it could inspect AS270218's holder and IPv6 route. The operation left records in the institutions surrounding it.

Legibility creates accountability without supplying a verdict. A named document can be checked against its source. A date can be compared with another date. A place can be found in a registration. An ASN can be queried. These properties make the operation researchable. They do not tell the reader what conclusion to reach about every aspect of the service.

What the sequence says about organization

The most revealing decision in 2019 was not a technical specification. It was the choice, visible through the filing, to seek a commercializer authorization in Hernandez's own name. That decision produced a legal identity with a term, defined dependencies and registration duties. The later concession materials show that the public role did not remain confined to that initial category.

The 2024 decisions were geographic and administrative. Two modifications attached the concession to La Lobera, Huanimaro, La Cantera, Paso de Carretas and San Isidro de Ayala through separately dated entries. The documents do not say who planned installations or how resources were allocated. They show the result that matters to the register: named service areas under a named concession holder.

The service code reflects a third class of decision. It organizes technical connectivity as a standardized relationship with defined terms, documents and procedures. That is not the same as obtaining permission or adding coverage. It is the work of making the offering repeatable at the consumer interface. Hernandez's name appears because the code assigns the provider role to him.

AS270218 reflects a fourth class. The network is represented in interdomain routing by a distinct number, with Hernandez named as holder and an IPv6 prefix visible in the checked data. Again, the record shows an outcome without exposing every internal decision behind it. The public fact is the routing identity and the observed prefix.

Taken together, these decisions describe organization through interfaces. The IFT interface accepts applications and records concessions. The service interface presents categories, contracts and account actions. The geographic interface consists of registered coverage modifications. The routing interface presents an ASN and prefix to the wider network system. Hernandez is the point of continuity across them.

This approach avoids two common errors in person profiles. One is to reduce the person to a job label unsupported by the record. The other is to turn institutional traces into evidence of personality. The available sources support neither move. They support a more exact account of what was filed, granted, defined, registered, presented and observed.

The record behind AS270218

AS270218 is the most compact symbol in the story, but it is not the whole story. On its own, the number identifies an autonomous system. Joined to the RIPEstat holder field, it identifies Sergio Hernandez Cisneros. Joined to the routing-status data, it identifies an IPv6-visible prefix at a dated observation. Only when placed beside the IFT and SIIVV materials does it become part of a fuller institutional profile.

The earlier documents explain why the name has regulatory meaning. The 2019 authorization establishes a first formal role and its dependence on concessioned network capacity. The later RPC page and service code establish a concession-holder role. The 2024 entries establish named coverage in the Huanimaro municipality. The website establishes the outward-facing SIIVV service surface. The routing endpoints establish the ASN layer.

No single source proves the entire chain. That is a strength when the sources are read correctly. The regulator is authoritative about the authorization and concession records. The provider's documents are direct evidence of its presented commercial framework. The website is direct evidence of the public interface. RIPEstat is evidence of the checked routing observation. Agreement across bounded sources produces a sturdier account than one expansive claim.

The chain also clarifies the organizational result. Hernandez is not visible only because his name appears on a page. He is visible in several distinct capacities that line up without becoming identical: recipient of a 2019 authorization, named concession holder in later records, provider in a service code, holder attached to coverage modifications and holder of an announced ASN. Each capacity carries its own constraint.

For readers trying to understand smaller network operations, this is the more durable lesson. Infrastructure is not made public by cables and radios alone. It becomes a public service through permissions, registered scope, contracts, service interfaces and routing coordination. The evidence may arrive as plain administrative records, but those records expose how responsibility is distributed and how an operation can be checked from the outside.

Sergio Hernandez Cisneros's public profile can therefore remain precise. It begins with a commercializer authorization in 2019. It later shows a concession record and service code, followed by two coverage modifications in 2024. It includes a website organized around fiber, wireless, payment and customer functions. It reaches the routing system through AS270218 and the IPv6 prefix 2806:401::/32 observed in July 2026.

That is enough to explain the person without writing a legend. The observable decisions concern legal form, service structure, geography and network identity. The constraints come from regulation, access to network capacity, formal procedure and the protocol boundary visible in routing data. The outcome is an operation that can be followed across documents and systems. The record is narrow, but it is not thin: read at full resolution, it shows how one named provider became institutionally, geographically and technically legible.